DineRoute + Caviar.
Send your Meta and Google ads to a page that routes premium diners straight into Caviar — with real conversion tracking on every click.
Caviar is the high-AOV second listing most restaurants forget.
Caviar is DoorDash's premium-tier marketplace, owned by DoorDash, sharing the same store IDs as DoorDash. If you list on DoorDash and qualify, you are usually on Caviar too — and Caviar diners average 25–40% higher check sizes because the brand attracts a more upscale customer. The problem is that nobody runs ads to Caviar specifically. They run ads to DoorDash and Caviar gets the ambient traffic.
DineRoute fixes that by surfacing both DoorDash and Caviar as separate buttons on your branded smart link. The diner picks the brand they prefer. High-AOV restaurants in major metros (NYC, SF, LA, DC, Chicago) routinely see 10–18% of their ad-driven orders go through Caviar at higher margin per order.
On every Caviar click, we fire a real conversion event back to Meta, Google Ads, GA4 and TikTok. You finally see what your Caviar-attributable ad CPA actually is — not the blended DoorDash + Caviar number that everyone has been running on for years.
How we resolve your Caviar store URLs.
Caviar URLs are derived from the matching DoorDash store ID. We resolve DoorDash via Google's Places API, parse the store ID, and construct the Caviar URL from the same ID. No scraping. No separate Caviar API.
- 1 You paste your restaurant URL into DineRoute
- 2 We fetch your Google Business Profile and extract the DoorDash `food_ordering` link
- 3 We parse the DoorDash store ID from the URL
- 4 We construct the matching Caviar URL using the same store ID — automatic ownership-map sibling
If your restaurant is not on Caviar (Caviar is invite-only), the button stays hidden until you list. We re-check every 24 hours.
doordash.com/store/trycaviar.com/store/What fires when a diner clicks "Order on Caviar."
Same architecture as DoorDash — Caviar is the second listing, separately attributed.
- 01
Diner taps "Order on Caviar" on your DineRoute page
Server-rendered anchor with the derived Caviar URL pre-baked. A 300ms intercept fires tracking before the handoff.
- 02
Browser pixels fire with a shared `event_id`
Meta Pixel, Google Ads gtag, GA4 and TikTok Pixel all fire `platform_click` with `platform=caviar` and a UUID `event_id`. Notice that this is separate from `platform=doordash` — you get distinct attribution.
- 03
Server-side conversion mirrors fire with the same `event_id`
Meta CAPI, Google sCAPI, GA4 Measurement Protocol and TikTok Events API. Browser + server deduplicated. `fbclid`, `gclid`, `gbraid`, `wbraid` forwarded.
- 04
Diner lands in Caviar with UTMs in the URL hash
`utm_source`, `utm_campaign`, `utm_medium` and the original `fbclid`/`gclid` appended as hash params. Caviar strips query params like DoorDash does, but preserves the hash.
What actually changes in Meta, Google and TikTok.
"Caviar click" as a high-value conversion
Tag `platform_click` (Caviar) with a higher conversion value than DoorDash (because AOV is higher). Meta starts preferring Caviar-leaning diners on premium campaigns.
"Caviar conversion" with full click-ID capture
Conversion tag fires with `conversion_label=caviar`. Useful for value-based bidding on premium restaurant campaigns.
`platform_click` Caviar vs DoorDash split
One report shows the Caviar-to-DoorDash ratio per campaign per location. Premium NYC/SF restaurants often see 15–22% of ad-driven orders flow through Caviar.
Every Caviar feature, preserved.
DineRoute is the smart link in front of your Caviar store — the diner lands in the standard Caviar experience and every native feature still works.
Pickup + delivery
Both order types preserved on the Caviar restaurant page after the diner lands.
DashPass eligibility
Caviar is DoorDash-owned — DashPass works on Caviar exactly as it does on DoorDash.
Premium / high-AOV brands
Caviar's diner base skews higher-income; AOV is typically 25–40% above DoorDash for the same store.
Scheduled delivery
Standard Caviar scheduled-delivery flow, untouched by DineRoute.
Major-metro coverage
Caviar serves NYC, SF, LA, DC, Chicago and a handful of other major metros.
DoorDash store ID derived
One DoorDash resolve gives you the matching Caviar URL automatically.
DineRoute → Caviar vs ads sent directly to Caviar.
What sending Meta ads through DineRoute changes versus pointing them at your Caviar store URL directly.
| Capability | DineRoute → Caviar | Meta ad → Caviar directly |
|---|---|---|
| Branded landing page | — | |
| Multi-platform routing | — | |
| Meta Pixel attribution | — | |
| Meta Conversions API (server-side) | — | |
| Custom domain | — | |
| Per-location analytics | — | |
| Conversion event back to Meta/Google | — | |
| UTM + click ID forwarded into Caviar | Partial — Caviar strips query params | |
| GA4 + TikTok events fired on click | — |
Caviar + DineRoute questions.
How long does it take to set up DineRoute for Caviar?
About 60 seconds. Because Caviar is owned by DoorDash and shares store IDs, we resolve your DoorDash URL via Google Places and automatically construct your matching Caviar URL.
What Caviar URL does DineRoute use?
Caviar URLs are derived from the matching DoorDash store ID. Caviar is DoorDash-owned and the two platforms share IDs one-to-one. We resolve DoorDash via Google's Places API, then build the Caviar URL from the same store ID.
What if my restaurant isn't on Caviar?
Caviar is invite-only and skewed toward premium/AOV-heavy restaurants in major metros (NYC, SF, LA, DC, Chicago). If you are not on Caviar, DineRoute hides the button automatically. Once you list, we surface it the next resolve cycle.
Are diners refunded through Caviar or through me?
Caviar (and behind it DoorDash) handles all refunds and customer service. DineRoute is just the smart link in front — we never touch the order or payment.
Do diners notice the redirect to Caviar?
No. The handoff is 300ms and lands them in the Caviar app or web directly. The whole flow feels native on mobile.
What if my Caviar URL changes?
Caviar URLs are derived from DoorDash store IDs, which are stable. If a store ID does change, we re-resolve every 24 hours and DineRoute updates automatically.
Should I prioritize Caviar over DoorDash on my smart link?
It depends on your check size. Caviar diners average a meaningfully higher AOV than DoorDash (it skews premium), so high-AOV restaurants often see better unit economics on Caviar. We let you reorder buttons on your smart link based on what wins for your brand.
What if my restaurant is geographically outside Caviar's coverage?
DineRoute hides the Caviar button automatically when the location is outside Caviar's coverage map. Diners only see ordering options that actually serve them.
DoorDash
Largest US delivery network. Pickup + delivery + group ordering, DashPass-eligible.
See integration →
Uber Eats
Global delivery network. Shares store IDs with Postmates so we route both at once.
See integration →
Grubhub
Strong in the Northeast. Shares store IDs with Seamless for dual coverage.
See integration →Two listings. One resolve. Two attribution streams.
60 seconds to publish. DoorDash and Caviar routed from one branded smart link, separately attributable in Meta and Google.
No credit card. 14-day trial. Cancel any time.