Shopify to MGID
Forward every Shopify 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 Shopify to MGID with Upstack Data
Shopify
One server-side setup that captures every Shopify storefront and checkout event, then forwards it to every tool you spend on.
Shopify 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 Shopify 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.
100% of conversions, server-side
Orders are captured from Shopify’s servers, so nothing is lost to ad blockers, ITP or a failed browser call.
Recognise returning customers
Shopify customer IDs, emails and phones are matched against the graph, so repeat buyers are identified across devices.
What actually moves
What Shopify carries, and what MGID needs.
Shopify and MGID describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what Shopify can put on an event, the right is what MGID can actually use.
Shopify sends
- order_id
- Shopify order and checkout token
- email / phone
- customer contact from checkout
- customer_id
- Shopify customer record, if they have one
- line_items
- products, variants and quantities
- total / subtotal / discount
- order economics
- 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 Shopify can send to.
- ShopifyMeta Conversions API
- ShopifyGoogle Ads Conversions
- ShopifyTikTok Events API
- ShopifyPinterest
- ShopifySnapchat
- ShopifyReddit
- ShopifyMicrosoft Ads
- ShopifyX
Other sources that feed MGID.
- WooCommerceMGID
- BigCommerceMGID
- Checkout ChampMGID
- RechargeMGID
- Custom stackMGID
- FunnelishMGID
- Lasso CommerceMGID
- Phoenix TechnologiesMGID
- SkioMGID
- Loop SubscriptionsMGID
- StripeMGID
- 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 Shopify talking to MGID.
A 15-minute walkthrough of this connector on your own account.