DineRoute + Favor.
Send your Meta and Google ads for Texas restaurants to a page that surfaces Favor alongside DoorDash and Uber Eats — and capture the diners loyal to the H-E-B network.
If you run a Texas restaurant, Favor is the listing your DoorDash-loyal customers ignore.
Favor is the Texas-native delivery network owned by H-E-B since 2018. It uses dedicated "Runners" instead of a gig-economy pool, which tends to produce better service quality and shorter delivery times. More importantly, Favor is integrated with the H-E-B loyalty ecosystem — and a huge percentage of Texas diners are deeply embedded in H-E-B brand loyalty. For many Austinites, "ordering Favor" is the default, not DoorDash.
Most Texas restaurants run their Meta ads to DoorDash or Uber Eats and Favor gets ignored. DineRoute surfaces all three on your branded smart link, with Favor positioned prominently for Texas-only campaigns. The diner picks. H-E-B-loyal customers will pick Favor most of the time. Out-of-state ad spend (where Favor is irrelevant) auto-hides the button.
On every Favor click — separately from DoorDash and Uber Eats — we fire a real conversion event back to Meta, Google Ads, GA4 and TikTok. Texas restaurants on DineRoute routinely discover Favor outperforms the marketplaces on CPA in Austin and San Antonio because Favor-loyal diners convert at a higher rate.
How we resolve your Favor restaurant URLs.
Favor URLs are not consistently published through Google's Places API yet (Favor's integration with Google Business is still maturing), so we use a hybrid approach: check Places first, fall back to manual paste, and auto-hide the Favor button for non-Texas locations.
- 1 You paste your restaurant URL into DineRoute
- 2 We check Google's Places API for a `food_ordering` action pointing at `favordelivery.com/`
- 3 If not found, you paste the Favor URL once — we validate it loads and the restaurant ID matches your address
- 4 DineRoute geo-checks every location: outside Texas, Favor is automatically hidden from the smart link
Manual paste is the current default for Favor. One-time, 10 seconds. Worth it for Texas restaurants.
favordelivery.com/What fires when a diner clicks "Order on Favor."
One client-side event, three server-side mirrors, attribution mirrored across all four ad platforms.
- 01
Diner taps "Order on Favor" on your DineRoute page
The Favor button is only rendered when the location is in Texas — outside Texas the button is suppressed at build time. 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=favor` and a UUID `event_id`. The Texas location slug is attached for per-city attribution.
- 03
Server-side conversion mirrors fire with the same `event_id`
Meta CAPI, Google sCAPI, GA4 Measurement Protocol and TikTok Events API receive the matching event. Browser + server deduplicated. `fbclid`, `gclid`, `gbraid`, `wbraid` forwarded.
- 04
Diner lands in Favor with UTMs in the URL hash
`utm_source`, `utm_campaign`, `utm_medium` and the original `fbclid`/`gclid` appended as hash params. Favor strips query params but the hash is preserved for any future postback integration.
What actually changes in Meta, Google and TikTok.
"Favor click" as a Texas-specific conversion
Optimize Texas-geotargeted campaigns toward `platform_click` (Favor). Austin and San Antonio restaurants often see Favor outperform DoorDash by 25–40% on Meta CPA because of the H-E-B loyalty halo.
"Favor conversion" with full click-ID capture
Conversion tag fires with `conversion_label=favor`. Useful for Texas-only campaigns where you want to bid separately on H-E-B-loyal diners.
`platform_click` Favor vs DoorDash vs Uber Eats
One report shows the three-way Texas split per campaign per city. Austin restaurants often see Favor take 30–45% of Texas-targeted ad-driven orders.
Every Favor feature, preserved.
DineRoute is the smart link in front of your Favor restaurant — the diner lands in the standard Favor experience and every native feature still works.
Delivery (Texas only)
Favor is delivery-first. Pickup is not the primary use case — diners come for the delivery experience.
H-E-B integration
Favor is H-E-B-owned. Texas diners often pair Favor delivery with H-E-B grocery — the loyalty crossover is real.
Runner-based fulfillment
Favor uses dedicated 'Runners' rather than a gig-economy pool — generally higher service quality.
Scheduled delivery
Standard Favor scheduled-delivery flow, untouched by DineRoute.
Texas-only coverage
Favor only serves Texas. DineRoute hides the button automatically outside Texas.
Per-location restaurant URLs
Multi-location Texas chains get one DineRoute link per location, each with its own Favor URL.
DineRoute → Favor vs ads sent directly to Favor.
What you gain by routing Favor through a branded multi-platform smart link versus sending Meta ads at the bare Favor URL.
| Capability | DineRoute → Favor | Meta ad → Favor 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 Favor | Partial — Favor strips query params | |
| GA4 + TikTok events fired on click | — | |
| Auto-hide outside Texas | — |
Favor + DineRoute questions.
How long does it take to set up DineRoute for Favor?
About 60 seconds. We resolve your Favor restaurant URL from Google's Places API where available. For most Favor restaurants you paste the URL once and we validate it — same outcome.
What Favor URL does DineRoute use?
We resolve your `favordelivery.com/` restaurant page URL. Favor URLs are not consistently surfaced through Google's Places API yet, so manual paste is currently the most common path — it's a one-time, 10-second step.
Why does Favor matter if I already have DoorDash and Uber Eats?
Texas. Favor was acquired by H-E-B in 2018 and is the dominant homegrown delivery brand in Texas — particularly in Austin, San Antonio, and the Houston suburbs. Texas diners with H-E-B loyalty often default to Favor for convenience and points. Surfacing Favor alongside DoorDash and Uber Eats consistently lifts orders 8–15% for Texas restaurants.
What if I open a new Texas location on Favor?
Add the location in your DineRoute dashboard. We attempt auto-resolve via Google Places, otherwise you paste the Favor URL once — we validate it and you're done.
Are diners refunded through Favor or through me?
Favor handles all refunds, cancellations and customer service exactly as today. DineRoute is just the smart link in front — we never touch the order or payment.
Do diners notice the redirect to Favor?
No. The handoff is 300ms and lands them in the Favor app or web directly. Texas diners often appreciate the consistency of a familiar brand experience.
What if my Favor URL changes?
Favor restaurant URLs are stable. We re-check every 24 hours via Places API where applicable, and you can manually update from your dashboard at any time.
What if my restaurant isn't on Favor?
If you are not in Texas, Favor is not available — DineRoute hides the button automatically. If you are in Texas and not on Favor, the button stays hidden until you list. Once listed, paste the URL and we surface it.
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 →
ChowNow
Commission-free direct ordering. Highest margin per order for the restaurant.
See integration →Texas runs on Favor. Your ads should too.
60 seconds to publish. Favor surfaced alongside DoorDash and Uber Eats — and auto-hidden outside Texas.
No credit card. 14-day trial. Cancel any time.