Skip to main content
  1. Home
  2. Connectors
  3. WooCommerce - MGID
WooCommerce MGID

Send every WooCommerce event to MGID, server-side

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

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 WooCommerce event reaches MGID. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from WooCommerce

Capture WooCommerce orders and customer events server-side and forward them to every platform you buy on.

See the WooCommerce integration
WooCommerceWhat it sends
  • order_idWooCommerce order number
  • billing_email / phonecheckout contact fields
  • customer_idWordPress user, when logged in
  • line_itemsproducts and quantities
  • order_totalorder value after discount

02 Understand

Resolved to one person before it leaves

Every WooCommerce 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 MGID

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

See the MGID integration
MGIDWhat it receives
  • 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

The catch

WooCommerce sites vary enormously in how checkout is built, and browser-side conversion tags break on custom checkouts more often than on hosted platforms.

Capturing on the server sidesteps the theme entirely.

Where to check in MGIDDelivery you can audit

MGID Dashboard Conversions

The postback log records each server-side conversion and the click it was matched to.

What changes

What changes when WooCommerce feeds MGID. Two gains on the MGID side, two on the WooCommerce side.

MGID

Server-side delivery

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

MGID

Identity-resolved events

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

WooCommerce

Every event, server-side

Storefront and checkout events are captured from WooCommerce on the server, independent of the browser.

WooCommerce

One setup, every destination

Connect WooCommerce once and forward to every ad platform, email tool and warehouse you run.

Setup

Live in under 20 minutes.

Connect WooCommerce once and every destination, MGID included, is forwarded the same resolved events.

Upstack dashboardExample
WooCommerce Data source Connected
MGID Destination Healthy
Read the full MGID setup guide
  1. 01

    Connect WooCommerce

    Capture WooCommerce orders and customer events server-side and forward them to every platform you buy on.

  2. 02

    Add the MGID destination

    Under Destinations, add MGID. Every resolved WooCommerce event is then forwarded to it.

  3. 03

    Check delivery to MGID

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

FAQ

Questions about WooCommerce and MGID.

How do I check that WooCommerce events are reaching MGID?

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

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 WooCommerce to MGID?

Most brands are live in under 20 minutes. Once WooCommerce is connected, every destination receives the same resolved events, MGID included.

Related connectors

See all 408 connectors

Get WooCommerce talking to MGID.

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

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