Skip to main content
Request a demo
  1. Home
  2. Integrations
  3. MGID
Upstack Data

MGID integration: identity-resolved conversions, sent server-side

Server-side conversions to MGID with hashed identifiers and restored click IDs, so a channel that is hard to attribute stops being invisible.

Request a demo Start free trial
Role
Destination
Category
Ad platforms
Pre-built connectors
12 sources
Plans
All plans

What Upstack sends

Every conversion reaches MGID with the identifiers it matches on. Captured on the server, resolved to a person, then sent.

In: from Shopify1 of 12 sources
  • order_idShopify order and checkout token
  • email / phonecustomer contact from checkout
  • customer_idShopify customer record, if they have one
  • line_itemsproducts, variants and quantities
  • total / subtotal / discountorder economics

Storefront events from the Upstack Pixel, orders directly from Shopify.

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.
Out: to MGIDOn every event
  • hashed email / phoneidentity matching on arrival
  • mgid_click_idcredit the click that drove it
  • external_idstable person across sessions
  • event_iddedupe against the browser pixel
  • value / currencyvalue-based bidding

Native conversions with identifiers attached.

See the set-up reference See all 12 sources How resolution works

About MGID

Upstack forwards conversions server-side with hashed identifiers and the restored click ID, resolved to a person first.

That gives MGID a consistent signal regardless of which publisher the click came from. The publisher is the variable the network cannot control on its own.

What MGID is

MGID is a native advertising network reaching audiences across regional and independent publishers.

Measurement quality varies by placement there, which makes clean first-party data unusually valuable.

How MGID works

MGID attributes conversions through its pixel and postback API within a click window it controls. What it receives is whatever the browser managed to send, which across a long tail of publisher sites is less than on a major platform.

What you can do with it

Three jobs this connector does inside MGID.

01

Send complete conversions

Conversions reach MGID through its server-side API with restored click IDs and hashed identifiers attached, so more of what you send is matched on arrival, and the conversions you never saw stop being invisible.

02

Optimize on the customer you want

Map any order attribute to the conversion MGID receives (profit rather than revenue, new customers rather than repeat buyers, high-value orders rather than every checkout), so the platform learns from the buyers worth acquiring.

03

Consistent signal across publishers

Every conversion is captured the same way regardless of placement, so performance differences reflect the placement rather than its tracking.

Pre-built connectors

12 sources connect to MGID. Whichever of these you run, MGID is one switch away.

See all connectors

Documentation

Set-up reference.

Set-up, event schema and field mapping for MGID as a destination.

FAQ

MGID integration questions.

What does Upstack send to MGID?

Server-side conversions to MGID with hashed identifiers and restored click IDs, so a channel that is hard to attribute stops being invisible.

How do I check that events are reaching MGID?

Open MGID › Dashboard › Conversions. The postback log records each server-side conversion and the click it was matched to.

Which plans include the MGID integration?

All plans. Upstack has three plans that scale with your order volume, and the same integrations are on every plan.

Which sources can send events to MGID?

12 sources: Shopify, WooCommerce, BigCommerce, Checkout Champ, Recharge, Custom stack, Funnelish, Lasso Commerce, Phoenix Technologies, Skio, Loop Subscriptions and Stripe. Each one has its own pre-built connector.

Will Upstack slow down my store?

Upstack’s own pixel loads asynchronously and fails silently, so it doesn’t hold up your pages. What each destination adds depends on its Tracking Method. The default, Browser + Server, loads that platform’s own tag on your store, in place of the copy you would otherwise install yourself, and also sends the same events from Upstack’s servers. Choose Server for any destination that offers it and its tag never loads, while its events still arrive from Upstack’s servers.

Similar integrations

Other Ad platforms integrations.

See all integrations

Get MGID tracking right.

A 15-minute walkthrough tailored to your stack and channels.

Request a demo Start free trial