Use cases
Restaurants and food with online ordering
A restaurant group takes orders on its website for delivery and pickup from several locations.
Illustrative example – not a real customer
The portrait they want
Who finds the menu from social or maps, which dishes and offers they open, and when they visit.
Typical problems
- It is unclear which promotions bring orders.
- Each location has its own website, so data is scattered.
- Busy hours make it hard to look at data during the day.
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
- add_to_cart
- checkout_start
- purchase
Example custom events
custom.location_selectWhich location people order from.custom.promo_code_applyPromotions that are used.
The portrait they can see today
- All location websites in one organization, each with its own reports.
- Today's traffic by hour, and earlier days in the 7 and 30 day ranges.
- Top menu pages.
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 soonOrders and revenue by location.
- Coming soonGroups of regular customers.
Try it on your own website
Create an account, add your website and publish your consent banner. No payment during the test phase.