Skip to content
Start free
Menu ▾
Advanced

Webhook CAPI relay

Push real order events from DoorDash and UberEats back to Meta as Purchase events. Enterprise feature.

What this does

DoorDash Developer and UberEats Marketplace APIs send webhooks whenever an order is placed at your restaurant. DineRoute receives the webhook, matches it back to the originating platform_click via device fingerprint and time window, and fires a Purchase event to Meta with the actual order value.

Result: Meta optimizes directly toward real orders instead of toward platform_click as a proxy. ROAS becomes literal.

Requirements

  • Enterprise plan
  • DoorDash Developer API approval (we help you apply)
  • UberEats Marketplace API approval (we help you apply)
  • Meta CAPI access token (same one from Meta Pixel + CAPI)

Approval timeline

  • DoorDash Developer: 2-4 weeks. Requires an MSA signed with DoorDash.
  • UberEats Marketplace: 3-6 weeks. Requires a business verification packet.

Your CSM runs both applications on your behalf. You sign the MSAs. We handle the rest.

How the relay works

  1. Customer taps a DoorDash button on your routing page. DineRoute fires platform_click with a device fingerprint and stores the fingerprint + timestamp.
  2. Customer places an order on DoorDash 8 minutes later.
  3. DoorDash webhook hits our edge with order ID, customer location, ticket total.
  4. We match the webhook back to the platform_click using location, device window, and item overlap.
  5. We fire a Meta Purchase event with the matched event_id, value, and currency. Match quality typically lands at 7-8 out of 10.

Match rate

Typical match rate is 62-74% on established accounts. Below 60% usually means the customer used a different device to complete checkout than the one that saw the ad (e.g., saw on mobile, ordered on desktop). We recommend a 48-hour click window in matching for those accounts.

Data retention

Webhook payloads are stored 90 days for matching and debugging, then purged. Match artifacts (event_id, platform, timestamp, value) retain 25 months to support Meta's attribution models. We never store customer PII from the webhook stream.