Skip to main content
Request a demo
  1. Home
  2. Connectors
  3. Stripe - The Trade Desk
Stripe The Trade Desk

Send events from your Stripe-billed app to The Trade Desk

Each event is resolved to a person against a 750M+ device graph before it reaches The Trade Desk, with restored click IDs, deduplicated conversions and delivery you can audit.

Request a demo Start free trial
US device IDs in the graph
750M+
Match rate on events
90%+
Identity window, per customer
Lifetime
Most brands are live
<20 min

How it flows

How a Stripe event reaches The Trade Desk. Sent from your app, resolved to a person, then forwarded.

01 Capture

Captured from Stripe

For apps that bill through Stripe, send payment and subscription events to Upstack with the Upstack Pixel and JavaScript SDK, resolved to a customer before they reach the tools you spend on.

See the Stripe integration
StripeWhat it sends
  • subscription_initial_purchaseyou fire it for the first subscription order
  • subscription_recurring_purchaseon invoice.paid for an existing subscription
  • payment_succeededmaps to invoice.paid or charge.succeeded
  • payment_refundedmaps to charge.refunded
  • amount / currencyamount in cents, with invoiceId and subscriptionId

02 Understand

Resolved to one person before it leaves

Every Stripe event is matched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer rather than two strangers.

How resolution works
Upstack DataResolved before it is sent
  • IdentityMatched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer.
  • customer_typeNew or returning, resolved before send.
  • DeduplicationBrowser and server copies of the same purchase collapse on event ID, so nothing is counted twice.
  • Bot and fraud filteringAutomated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.

Ad platforms accept almost anything and tell you very little. These controls exist so you can see what was sent and what was accepted, rather than inferring it from a reporting gap.

03 Activate

Delivered to The Trade Desk

Forward identity-resolved conversions to The Trade Desk, so programmatic bidding is trained on real buyers rather than on modeled cohorts.

See the The Trade Desk integration
The Trade DeskWhat it receives
  • hashed email (UID2)the identity framework TTD bids against
  • ttd_click_idcredit the impression or click
  • event_iddedupe across the pixel and server feed
  • value / currencytrain bidding on revenue
  • external_idstable person across sessions

The catch

A retried payment produces several Stripe objects for one purchase.

Forwarding each as a conversion inflates reported performance by the retry rate, which is highest on exactly the campaigns bringing in the least reliable payment methods. Fire the Upstack event when Stripe reports the payment succeeded (invoice.paid or charge.succeeded), so only the settled payment becomes a conversion.

Where to check in The Trade DeskDelivery you can audit

The Trade Desk Data Conversions

The conversion feed reports match rates, which is the number worth watching after a server-side switch.

What changes

What changes when Stripe feeds The Trade Desk. Two gains on the The Trade Desk side, two on the Stripe side.

The Trade Desk

Server-side delivery

Events reach The Trade Desk through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.

The Trade Desk

Identity-resolved events

Events sent to The Trade Desk carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.

Stripe

Subscription purchases as events

Fire subscription_initial_purchase for the first order and subscription_recurring_purchase each time a renewal is paid, so first orders and renewals are reported separately.

Stripe

Payments and refunds

payment_succeeded, payment_failed and payment_refunded each map to a Stripe event (invoice.paid or charge.succeeded, invoice.payment_failed, charge.refunded), so money events reach Upstack when your app fires them.

Setup

Live in under 20 minutes.

Connect Stripe once and every destination, The Trade Desk included, is forwarded the same resolved events.

Upstack dashboardExample
The Trade Desk Destination Healthy
Read the full The Trade Desk setup guide

  1. 01

    Install the Upstack Pixel and SDK

    Add the Upstack Pixel to your app, then fire the subscription and payment events with the JavaScript SDK when Stripe reports them, such as subscription_recurring_purchase when invoice.paid fires for an existing subscription.

  2. 02

    Add the The Trade Desk destination

    Under Destinations, add The Trade Desk. Every resolved Stripe event is then forwarded to it.

  3. 03

    Check delivery to The Trade Desk

    Every conversion is inspectable from the moment it fires to the moment the platform confirms it.

FAQ

Questions about Stripe and The Trade Desk.

How do I check that Stripe events are reaching The Trade Desk?

Open The Trade Desk › Data › Conversions. The conversion feed reports match rates, which is the number worth watching after a server-side switch.

Will a purchase be counted twice?

No. Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.

How long does it take to connect Stripe to The Trade Desk?

Most brands are live in under 20 minutes. Once Stripe events reach Upstack, every destination receives the same resolved events, The Trade Desk included.

Related connectors

See all 408 connectors

Stripe to

All 34 Stripe connectors

The Trade Desk from

The Trade Desk integration

Get Stripe talking to The Trade Desk.

A 15-minute walkthrough of this connector on your own account.

Request a demo Start free trial

21-day free trial, no card. Month to month.