Tracking that counts what matters to a restaurant
Calls, direction requests, booking clicks, online orders. If they aren't counted, nobody can say which channel brought the table.
Tracking: GA4, Google tag, Meta Pixel
Calls, directions and booking clicks counted, so ad money isn't a guess.
HOW YOU SEE IT WORKINGThe events show up in GA4 and in the ad platforms, and feed the results page.
Sound familiar?
Ads running with no pixel on the site.
A Google Ads tag installed and nothing measuring the visits.
Bookings happening on another site that nobody connected.
The same tag installed twice, counting every visit double.
How bee6 runs it
- 01
Audit what is on the site today and what actually fires.
- 02
Install GA4, the Google tag and the Meta Pixel with the Conversions API.
- 03
Define the events that matter: call, directions, booking click, order click.
- 04
Connect the booking and ordering pages where the tools allow it.
- 05
A consent banner that respects the visitor's choice.
Questions owners ask
What is the Conversions API for?
The Pixel reports from the browser, and browsers and ad blockers cut part of that. The Conversions API sends the same events from the server, so fewer get lost.
Is there a Google pixel?
Google's version is the Google tag, which feeds GA4 and Google Ads. Same idea, different name.
Can you track bookings made on OpenTable or Resy?
The click to book, always. The finished booking depends on the tool, and we check it at onboarding.