Alongside, not instead
Every event carries the same event ID your Meta pixel uses, so Meta's own deduplication treats the pair as one conversion. Browser and server together, never double-counted.
Your ads know who clicked.
Not who showed up — or what they spent.
The problem
Browser tracking is the weakest link in your funnel.
A browser pixel has to survive an ad blocker, a cookie policy, a consent banner and an OS privacy prompt before it reports a single booking. Plenty don't survive all four — and the ones that don't are invisible to you, not flagged as missing.
Browser pixel only
52 of 100 bookings reported
18 ad blockers13 cookie expiry10 consent declined7 app tracking opt-out
OpenJug, server to server
100 of 100 bookings reported
The bigger problem
Even when it fires, it only ever sees the booking.
A reservation isn't one moment, it's four. The browser is present for exactly one of them — the click. Everything that tells you whether that booking was worth anything happens hours or days later, on OpenTable's servers, long after the browser tab is closed.
-
Day 0 · 14:02
Booked
Table for six, Saturday 7pm
Browser pixel OpenJug -
Day 3 · 19:04
Arrived
Seated — or never showed
Browser missed OpenJug -
Day 3 · 19:06
Covers confirmed
Six became eight
Browser missed OpenJug -
Day 3 · 21:40
Spent $480
The number that matters
Browser missed OpenJug
Browser pixel 1 of 4
OpenJug 4 of 4
So your campaigns optimise toward bookings, not diners. A no-show and the best table of the month look identical to Meta — same event, same value, same signal to go find more people like them.
The fix
Server to server. No browser in the path.
OpenTable's servers tell ours about every reservation as it happens, and again as it changes. We match the guest, hash the details, and send the event straight into each platform's conversion API — including Meta's, alongside the pixel you already run.
Nothing to block
There's no script on a page, so there's no ad blocker to dodge, no cookie to expire and no tracking prompt to lose. The reservation is already confirmed when we send it.
Fires more than once
Booking, arrival, final covers, real spend — each becomes its own event, so you can optimise toward the guests who actually show up and order.
Signal depth
The difference isn't accuracy. It's what's inside the event.
Two conversions can both say "booking" and be worth completely different amounts to the algorithm trying to find your next customer.
Browser pixel event
- +Event name
- +Page URL & timestamp
- +Browser cookie ID — if it survived
- —Party size
- —Showed up / no-show
- —Covers actually seated
- —Amount spent
- —Cancellation
OpenJug server event
- +Confirmed reservation
- +Venue & booking time
- +Hashed guest match (email, phone)
- +Party size
- +Showed up / no-show
- +Covers actually seated
- +Amount spent
- +Cancellation
Where it goes
One connection. Every platform you actually run.
OpenTable's built-in tags cover two destinations, in the browser. The same reservation data, sent server-side, reaches every platform you spend on — with the depth the browser could never carry.
Built into OpenTable — browser side
Meta Pixel
Google tag
Two destinations, one event each, subject to everything above.
With OpenJug — server side
Meta CAPI
Google Ads
TikTok
Pinterest
LinkedIn
Every one of them gets the full event — party size, covers seated, real spend — not just the click.
What it takes from you
We connect it. You never touch it.
Nothing changes inside your OpenTable account. There's nothing to install on your website, no tag manager to open, and no new dashboard for your team to learn. We set it up against your venues and your ad accounts, confirm the events are landing, and from then on it simply runs.
For OpenTable partner managers
Something worth recommending to your restaurants.
OpenJug is built on OpenTable's own documented reservation APIs — no scraping, no unofficial endpoints, nothing bolted onto the booking flow.
- +Costs OpenTable nothing and adds no support burden — we handle setup and monitoring for the venue.
- +Gives the restaurants on your book a visible reason their marketing spend is working harder.
- +Makes OpenTable the source of truth for their ad reporting, not just their bookings.
- +Happy to walk your team through the integration before you put it in front of anyone.
Next step
Bring your RID. We'll show you what you're missing.
Twenty minutes, your restaurant's OpenTable ID, and we'll walk through exactly which bookings your ad accounts are seeing today and which ones they aren't.