A restaurant client sent us a Meta Ads Manager screenshot last month. Two million impressions, thirty-eight thousand link clicks, zero purchases.

Their DoorDash dashboard showed ninety-four thousand dollars in delivery that same month.

Those two dashboards never spoke to each other. That is the whole problem.

The walled garden

When a customer taps your Instagram ad and lands on DoorDash, DoorDash owns the rest of the session. Meta’s Pixel does not load on doordash.com. DoorDash’s customer data does not flow back to Meta. The ad platform is blind from the moment of the tap forward.

What Meta’s optimizer gets instead is a link click. Link clicks are Meta’s default fallback event, and they correlate with almost nothing useful. People who tap ads to read the caption, people who tap by accident, people who tap and never load the destination page — all counted as link clicks. The optimizer learns to find more of that.

What platform_click actually solves

DineRoute inserts a routing page between your ad and the platform. On that page, a custom Pixel event called platform_click fires the moment a customer taps a platform button. The event carries:

  • action_source: website
  • user_data: IP, user agent, fbc, fbp
  • custom_data.platform: doordash or ubereats or grubhub

Meta’s algorithm now has a real event to optimize toward. Not every click — only clicks where the customer picked a delivery platform. That is an order-intent signal. It correlates tightly with actual orders, which is why campaign CPA drops 20-40% once the learning phase stabilizes on the new event.

Why not just fire a Lead event?

You could. Most agencies do. “Lead” is a generic Meta standard event that applies to newsletter signups, brochure downloads, quote requests, anything. The optimizer gets weak specificity and ends up learning the wrong patterns.

Custom events — named precisely to your conversion flow — give Meta’s algorithm much sharper signal. platform_click tells the model exactly what happened: this customer picked a delivery platform on a branded routing page. That specificity is how the model learns which creatives, which audiences, and which placements drive real order intent instead of browse-only traffic.

The webhook layer

There is a second layer on Enterprise accounts. DoorDash Developer and UberEats Marketplace APIs will send you a webhook when an order is placed. DineRoute catches the webhook, matches it back to the originating platform_click, and fires a Meta Purchase event with the actual ticket value.

Now Meta optimizes directly toward orders, with real dollar values. ROAS becomes literal instead of estimated.

The fix takes ten minutes

Paste your platform URLs into DineRoute. Paste your Meta Pixel ID and CAPI token. Point your campaigns at the routing page. That is the whole setup.

We are not reinventing your stack. We are fixing a measurement gap that has cost every restaurant running Meta ads ROAS for the past decade.

Start a free trial.