Stripe to MGID
Forward every Stripe event to MGID server-side, resolved to a person against a 750M+ device graph — with restored click IDs, deduplicated conversions and delivery you can audit.
Connection
Connect Stripe to MGID with Upstack Data
Stripe
Capture every Stripe payment and subscription charge from the server, resolved to a customer before it reaches the tools you spend on.
Stripe integration
MGID
Server-side conversions to MGID with hashed identifiers and restored click IDs, so a channel that is hard to attribute stops being invisible.
MGID integrationWhat changes
What changes when Stripe feeds MGID.
Server-side delivery
Events reach MGID through its server API, not the browser — so ad blockers, ITP and consent banners don’t cost you conversions.
Identity-resolved events
Every event sent to MGID carries a resolved customer, matched against a 750M+ device graph.
Every event, server-side
Storefront and checkout events are captured from Stripe on the server, independent of the browser.
One setup, every destination
Connect Stripe once and forward to every ad platform, email tool and warehouse you run.
What actually moves
What Stripe carries, and what MGID needs.
Stripe and MGID describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what Stripe can put on an event, the right is what MGID can actually use.
Stripe sends
- payment_intent / charge_id
- the settled payment, not the attempt
- email / phone
- customer contact from the payment method
- customer_id
- Stripe customer record, where one exists
- line_items / price_id
- what was bought, including subscription items
- amount / currency / refunded
- the amount that actually settled
- customer_type
- new or returning, resolved before send
MGID receives
- hashed email / phone
- identity matching on arrival
- mgid_click_id
- credit the click that drove it
- external_id
- stable person across sessions
- event_id
- dedupe against the browser pixel
- value / currency
- value-based bidding
Delivery you can audit
How you know it is working.
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.
Per-event inspection
Every conversion is inspectable from the moment it fires to the moment the platform confirms it.Deduplication
Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.Bot and fraud filtering
Automated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
Where to check in MGID
MGIDDashboardConversions. The postback log records each server-side conversion and the click it was matched to.
Related connectors
Other places Stripe can send to.
- StripeMeta Conversions API
- StripeGoogle Ads Conversions
- StripeTikTok Events API
- StripePinterest
- StripeSnapchat
- StripeReddit
- StripeMicrosoft Ads
- StripeX
Other sources that feed MGID.
- ShopifyMGID
- WooCommerceMGID
- BigCommerceMGID
- Checkout ChampMGID
- RechargeMGID
- Custom stackMGID
- FunnelishMGID
- Lasso CommerceMGID
- Phoenix TechnologiesMGID
- SkioMGID
- Loop SubscriptionsMGID
- Everything MGID can take12 sources feed MGID, and the setup is the same for each one.MGID integration
- How resolution worksEvery event matched against a 750M+ device graph before it is forwarded.Upstack Signal
- What it costsThree plans that scale with your order volume. Every connector is on every plan.See pricing
Get Stripe talking to MGID.
A 15-minute walkthrough of this connector on your own account.