MGID postback integration

MGID can optimize across its publisher sites only if conversions come back to the click that bought them. Send MGID its postback straight from your LanderLab page, with its click ID, the moment a lead submits.

  • Webhook
  • Landing pages, Quiz funnels, Workflows (beta, by HTTP Request)

Why connect it

Why MGID and LanderLab

  • Conversions MGID can optimize on

    Every submit sends MGID a conversion tied to the exact click, so its optimization and reports work from leads, not clicks.

  • Server-to-server, so blockers don't matter

    A postback goes from LanderLab's server to MGID's. Ad blockers, cookie limits and privacy settings in the browser don't touch it.

  • No tracker needed for a one-page funnel

    For an advertorial into a lead form, LanderLab captures the click ID and fires the postback itself. Add a tracker when the funnel needs one, not before.

  • Revenue on every conversion

    MGID's postback takes an optional revenue value, shown in your account currency, so return on spend sits next to the cost.

  • A postback only for qualified leads

    The HTTP Request node in Workflows (beta) can send the postback only when the answers qualify, so MGID optimizes toward leads your buyer pays for.

  • Up to three goals per campaign

    MGID tracks up to three conversion goals by postback, so a qualified lead can count separately from a raw submit.

MGID on your landing pages

MGID sells native traffic across a large network of publisher sites, and like every native network it rewards the buyer who reports conversions: its optimization, its reporting and your own decisions about which widgets to keep all depend on knowing which clicks became leads.

MGID's preferred way to hear about a conversion is a server-to-server postback carrying the click ID it put on your URL. LanderLab can send it directly: a hidden field captures MGID's click ID when the visitor lands, and the page's webhook calls MGID's postback when the lead submits. For a simple funnel there's no tracker in the middle and no Zap to pay for.

It suits native buyers running advertorials into lead forms or quizzes: home improvement, insurance, finance and ecom opt-ins.

MGID S2S conversion tracking without a tracker

MGID puts its click ID on your landing page URL. A hidden field saves it with the lead, and when the form is sent, the page's webhook calls MGID's postback with it, so MGID counts the conversion on the exact click that bought it.

MGID's own help calls postback the more reliable method because it isn't affected by ad blockers, browser limitations or privacy settings. On a landing page that's exactly where pixel data goes missing.

Optimize MGID on leads that pay

A raw submit and a lead your buyer accepts are different conversions. Send the basic postback for every lead, and route a second goal through a workflow: a Lead trigger, an If on the answers that make a lead sellable, and an HTTP Request node that fires the qualified goal only on that branch. MGID then reports and optimizes on the goal you choose.

Each MGID campaign can count unique or non-unique conversions per goal. For lead gen, unique is usually right: one lead per click.

Widgets and sites judged on cost per lead

Native traffic varies by placement more than by anything else. With conversions in MGID, the placements that send clicks and no leads show up quickly, and you can cut them before they eat the test budget. Keep MGID's other tracking values in hidden fields too and every lead in your CRM carries its source.

Click IDs that survive the funnel

If the advertorial links on to a quiz or an offer, Pass Through URL Params forwards MGID's click ID and your UTMs to every link, so the page that captures the lead still has the click ID it needs for the postback.

Use cases

Ways to use MGID on paid traffic

  • 01

    Window replacement quotes

    An advertorial on home sites leads to a quote form. Each submit posts back to MGID with its click ID, and a second goal fires only for homeowners in the installer's service area.

  • 02

    Final expense insurance

    A story aimed at older readers leads to a short quiz. MGID optimizes on the qualified goal sent by a workflow, not on every submit.

  • 03

    Ecom opt-in before the store

    A product story collects an email for a discount code first. The postback carries the opt-in to MGID with a revenue value, and Pass Through URL Params keeps the click ID on the way to the store.

FAQ

MGID integration FAQ

Anything not here, ask us.

MGID and LanderLab

Does LanderLab integrate with MGID?

Yes, through the page's Webhook integration: when a lead submits, it sends MGID's S2S postback with the click ID a hidden field saved from the URL.

Do I need a tracker or Zapier to post back to MGID?

No. When the form is on your landing page, LanderLab captures the click ID and calls the postback itself. Use a tracker if your funnel spans other sites.

Can I post back only qualified leads?

Yes. A workflow with an If or Filter ahead of an HTTP Request node sends the postback only for the leads that pass.

Can I send revenue to MGID?

Yes. MGID's postback accepts an optional revenue value, which you can send as your payout per lead.

What if a postback fails?

The lead is still saved in LanderLab's Leads tab, unless Lead Compliance Delivery is on, so you have the click ID on record.

Other integrations

Plug in the rest of your stack.

Connect MGID and launch your next page.

Build the page, switch MGID on and send your ads to it. Free to start, no card.

From one prompt to qualified leads

Watch one prompt become a live solar quote funnel, every lead routed to your buyer, and the leaks flagged before they eat your budget.

0:00
0:59