Home
Connectors
Funnelish - MGID

Send Funnelish funnel events to MGID

Q: How do I check that Funnelish events are reaching MGID?

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

Q: Will a purchase be counted twice?

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

Q: How long does it take to connect Funnelish to MGID?

Most brands are live in under 20 minutes. Once Funnelish events reach Upstack, every destination receives the same resolved events, MGID included.

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.

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 Funnelish event reaches MGID. Tracked on the funnel page, resolved to a person, then sent.

01 Capture

Captured from Funnelish

Add the Upstack Pixel to your Funnelish funnels to track what shoppers do there. When Funnelish creates the order in Shopify, Upstack records it like any other Shopify order.

See the Funnelish integration

FunnelishWhat it sends

page / eventsfrom the Upstack Pixel in each funnel’s head
fbclid / gclid / ttclidclick IDs kept on the way to checkout
order_idthe Shopify order Funnelish creates
order sourceshows as Funnelish in Upstack reports

02 Understand

Resolved to one person before it leaves

Every Funnelish 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

Resolved 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

Funnel pages sit outside your Shopify theme, so the Upstack app embed doesn't run on them, and click IDs such as fbclid, gclid and ttclid are easily dropped on the way to checkout.

Add the Upstack Pixel to each funnel and keep the click IDs on the links to checkout. The order itself reaches Upstack when Funnelish creates it in Shopify, counted once per Shopify order ID.

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 Funnelish feeds MGID. Two gains on the MGID side, two on the Funnelish 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.

Funnelish

Funnel pages tracked

The pixel loads in the head of every funnel page, so visits and the events you configure are recorded on pages your theme never touches.

Funnelish

One setup, every destination

Connect Funnelish once and forward to every ad platform and email tool you run.

Setup

Live in under 20 minutes.

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

Upstack dashboardExample

MGID Destination Healthy

Read the full MGID setup guide

01

Add the Upstack Pixel to each funnel

In Funnelish, add the Upstack Pixel snippet to each funnel as a tracking code placed with Append To Page Head. If the funnel links to Shopify, add the script that keeps click IDs and UTMs on the link.
02

Add the MGID destination

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

Check delivery to MGID

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