OpenTable · Conversion tracking
Conversion tracking for OpenTable reservations
A restaurant on OpenTable gets reservations from two places at once: its own website widget, and the OpenTable network where diners already browse. Only the first is plausibly yours to attribute to an ad, yet both end up in the same reservation book. Before any tag goes in, the job is to tell those two apart and decide whether a booking or a seated cover is the thing you are paying for.
✓ 30-minute call · No commitment · You leave with a written remediation plan even if we’re not the right fit.
Written guarantee
95%+ conversion accuracy on OpenTable
Measured against your own order records at handover. Miss it and we keep working at no cost until it’s met.
Built on — and certified for — the platforms that matter
Stape
Pro Partner
Meta
Tech Provider
Tag Manager
TikTok
Events API
Microsoft
UET Partner
CAPI Partner
CAPI Partner
Built on the same partner stack used by enterprise DTC brands.
By the numbers
No fake testimonials.Just the math.
70+
Platforms supported
Shopify · Woo · Magento · BigCommerce · 65 more
8+ / 10
Meta EMQ guaranteed
in writing — keep working free until hit
2–4d
Build to live
accurate data flowing within 7 days
$0
Monthly fees, ever
one-time fixed price · you own the stack
400d
Cookie lifetime
max RFC 6265bis allows · 57× Safari ITP
9
Ad channels covered
Meta · Google · TikTok · MS · LI · Pin · Snap · Reddit · X
95%+
Tracking accuracy
verified vs Stripe · GA4 · ad-platform reports
30 min
Free founder call
no SDR · no pitch deck · written remediation plan
Every figure above is either a commitment we put in writing or a countable fact. What your own setup is losing is not on this list, because we haven’t measured it yet — that happens on the call, against your own order records.
Real clients · real videos · real outcomes
Don’t take our word for it. Watch the receipts.
Founders, marketers, and agency owners describing the before-and-after of their OpenTable tracking rebuild — in their own words, on camera.
Where OpenTable reporting misleads
Network bookings mixed with website bookings
If both land in one count, your ads get credit for diners OpenTable sent.
A widget that may leave your domain
If it opens or redirects to OpenTable, your cookies don't follow.
Bookings that never sit down
Friday no-shows and same-day cancellations get counted as wins.
Party size ignored
A two-top and a twelve-top are the same conversion unless covers are sent.
Architecture
What OpenTable actually lets you do
OpenTable's tracking options for restaurant websites aren't publicly documented in detail, so we confirm each of these on your account.
Step 1
Check how your widget behaves
Inline on your page, a popup, or a redirect to OpenTable's site; each needs a different approach.
Step 2
Check whether a tag can fire on widget completion
If the widget reports nothing back to your page, the browser side ends at the click.
Step 3
Check whether reservations carry a booking source
Website versus network is the split everything else depends on.
Step 4
Check what the reservation export includes
Party size, status, source and date per reservation.
Step 5
Check OpenTable's integrations list for your plan
Some connections are partner-specific; confirm before relying on any.
Diagnostic sequence
Tracing an OpenTable attribution gap
Start with the source split, because it explains the biggest discrepancies.
- 1
Split last month's reservations by source
If ads claim more than your website widget produced, they're taking network bookings.
- 2
Book a table through your own site
Watch where the widget sends you and which tags fire.
- 3
Compare booked against seated
The difference is your no-show and cancellation rate.
- 4
Check covers on the conversions
If every reservation carries one value, larger parties are undervalued.
- 5
Look for host-entered phone reservations
They should never show up as ad conversions.
Source-of-truth validation
The OpenTable QA evidence
On a real reservation through your own website, followed to the service date.
- A reservation through your website widget confirmed in OpenTable with its source.
- Network reservations confirmed absent from ad conversions.
- Seated covers reconciled per reservation against each ad platform.
- A no-show confirmed to drop out after service.
- Host-entered phone reservations confirmed excluded.
- Matched reservation by reservation over a fully closed window.
- Run again a month later, and whenever OpenTable or your web developer changes the widget.
Straight talk
When OpenTable tracking is overkill
Some restaurants should not spend money on this.
- If nearly all your reservations come from the OpenTable network, ad attribution on your website affects very few tables.
- If you run ads only to announce a new opening, a UTM-tagged link and the source split in OpenTable may be all you need.
- If phone bookings dominate, invest in how the host records the source first.
- If you just want monthly covers by channel, check OpenTable's own reporting before paying anyone.
Who this is for
Honest about who we’re a fit for.
We don’t take every project. Here’s how to tell if we’re right for you.
You’re a great fit if…
- You run OpenTable (or are migrating to it)
- You spend $5K+/month on paid ads (Meta, Google, TikTok, Microsoft, LinkedIn)
- Your reported ROAS doesn’t match what your bank account is saying
- You want to own your tracking stack — no monthly SaaS fees forever
- You have 2–4 days to do this once and never think about it again
Skip us if…
- You spend less than $500/month on paid ads (browser pixel is fine)
- You want a SaaS dashboard with monthly fees forever (Triple Whale, Hyros)
- You need attribution modeling — we fix the data foundation, not multi-touch reports
- You want a 6-month enterprise consulting engagement (we ship in 4 days)
- You expect us to manage your ad accounts (we don’t — that’s a different service)
If you’re still unsure,book the call anyway— we’ll tell you straight whether we can help.
What changes on OpenTable
Website-widget reservations isolated
Server-sideThe only bookings an ad can reasonably claim.
Covers as the value
8+ EMQParty size rides on each reservation, so larger tables count for more.
Seated status, not just booked
DedupedNo-shows are removed after service.
OpenTable event map
Reserve button clicked on your site
The last moment your own tags definitely see.
Reservation made from the website widget
With date, time and party size.
Reservation made on the OpenTable network
Reported, but kept out of ad conversions.
Guest seated
The conversion, valued by covers.
No-show or cancellation
Pulled back once the service date has passed.
Pick the package that fits your ad spend
Fixed-fee, no surprises. If your ad spend is meaningful,server-side tracking is what we recommend— it’s the only setup that survives iOS, Safari ITP and ad blockers.
Browser-side starter
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Save $18K–$120K over 5 years vs Triple Whale / Hyros
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations reversed everywhere
- Monitoring on every destination
Not sure which tier fits?Book a 30-min scoping call— we’ll tell you straight, no upsell pressure.
How it works
Built in 2–4 days. Accurate data within 7.
We deliver the entire 1st-party server-side stack in 2–4 business days. You start collecting accurate, deduped conversion data the moment it goes live — and within 7 days every signal is flowing cleanly to Meta, Google, TikTok and the rest.
Kickoff + audit
30-min call. We map your current pixels, GTM, dataLayer, consent setup, and ad-platform integrations. You get a written report of every leak.
Build the stack
Server-side GTM container deployed on your subdomain. Meta CAPI · Google EC · TikTok Events API · Microsoft UET wired. Identity match + dedup configured.
QA + go-live
Live-fire test purchases across every funnel step. Meta EMQ verified at 8+. Tag Assistant + Pixel Helper passes. Side-by-side report delivered.
Verify accuracy
Your data flows clean. Within 7 days every signal — Meta, Google, TikTok, Microsoft — is fully accurate. Notion runbook + Loom walkthrough handoff.
Got questions?
The honestanswers.
No buzzwords, no upsell. If we don’t know, we say so.
01Can our Meta Pixel see an OpenTable reservation?
Only if the widget on your site lets a tag fire when the booking completes, which we check on your setup. If it doesn't, the reservation is sent server-side from OpenTable's records instead.
02Do OpenTable network bookings count as ad conversions?
They shouldn't, by default. Diners booking through the network found you there, and counting them makes your ads look better than they are.
03Should we send party size?
Always. Covers are what you staff and buy for, so a table for eight should count for more than a table for two.
04What about no-shows?
Count the guest once they're seated. Booked-but-never-arrived reservations are reversed after the service date.
05Does this cover private dining and events?
If they're booked through OpenTable, they can be a separate conversion with their own value. If they come in by email, that's a lead-tracking job, not a widget one.
Still have questions?Book a 30-min call— bring them all.
The call
What happens on your free 30-min call
No pitch deck, no SDR, no upsell pressure. Founder-led. Bring your ad-platform screens and yourOpenTable setup — we’ll work through it together.
Min 1–5
We get the lay of your store
What you sell, what you spend on ads, who handles dev. Quick context-gathering — no questionnaire upfront.
Min 5–15
We audit your tracking live
Screen-share. We open your Meta Events Manager, GTM, and ad reports. You see exactly which conversions are leaking.
Min 15–25
We map a fix
What needs rebuilding, what stays. The exact OpenTable setup we'd ship and what it would recover for you.
Min 25–30
Decide. Or don’t.
If we're a fit, we send a 1-page proposal in writing. If not, you walk away with a free remediation plan you can hand to anyone.
Know which tables your ads actually filled
In a free 30-minute call we split your OpenTable book by source with you, book a test table through your site, and write up what is worth fixing.
Free · 30-min consultation · No commitment · Replies in under 2 hours · Available worldwide via WhatsApp
95% tracking accuracy guarantee
Free 30-min consultation · from $400 · 1st-party server-side
95% guarantee · from $400
