Use cases
Travel and booking agency
A small travel agency sells tours online and receives many enquiries through a form.
Illustrative example – not a real customer
The portrait they want
Which destinations and campaigns draw dreamers, and which of them come back ready to enquire.
Typical problems
- Seasonal campaigns are hard to compare.
- People view many tours and send an enquiry days later.
- The team does not know which destinations get attention but few enquiries.
What applies today
Consented first-party tracking
The banner asks per purpose, nothing is recorded before a choice, and the server checks consent for every event.
Traffic, sources and pages reports
Visitors, sessions and page views over time, channels and campaigns, and the most viewed pages.
Standard and custom events
product_view, add_to_cart, checkout_start, purchase and more, plus custom.* events you declare in the console.
Several websites in one organization
Each website has its own reports, managed by the same team with roles.
Sample setup
Standard events
- page_view
- product_view
- search
- form_submit
- checkout_start
- purchase
Example custom events
custom.date_checkDeparture dates people check.custom.itinerary_downloadItineraries people download.
The portrait they can see today
- Most viewed tour pages by date range, including last month and the last 90 days.
- Sessions by campaign for seasonal promotions.
- Reports in the agency's own reporting time zone.
Coming soon
- Coming soonNew and returning visitors, to see who comes back.
- Coming soonBuying signals from the events above (views, carts, checkouts, purchases).
- Coming soonAutomated traffic filtered out (in progress).
- Coming soonBooking value reports.
- Coming soonGroups of past travellers who have not booked again.
Try it on your own website
Create an account, add your website and publish your consent banner. No payment during the test phase.