MGID teasers and widgets,measured on revenue

The MGID template captures the click ID, click price and teaser, widget and campaign macros. ClickFlare posts conversions with revenue to a.mgid.com for up to three goals per campaign, and the cost integration pulls actual spend by campaign, content and publisher.

Start for free

Read the setup guide

MGID

Native ad network

At a glance

How it connects

S2S postback + cost API (Client API ID and access token)

What syncs

Conversions and revenue out; cost per click and by API in

Sync schedule

Real time, per conversion

Key parameters

click_id, click_price, teaser_id, widget_id, campaign_id

Works with

Native teasers in publisher widgets

Good to know

Goal names use Latin letters and numbers only

Native ad network

Up to 3 goals

Per-click cost

Cut MGID widgets that cost more than they pay

Widget-level decisions

widget_id shows which publisher placements convert, so you can block them or adjust their bids in MGID.

Cost from the first click

click_price passes each click's cost in the URL, so ROI shows as soon as traffic starts.

Exact spend when it matters

MGID discounts some clicks after the fact. The cost integration pulls actual spend from MGID's API and takes priority over the URL value.

How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

Your ad

Visitor clicks

Ad on MGID

ClickFlare

Click recorded

A unique cf_click_id is created

Your offer

Conversion

Lead, sale or custom event

ClickFlare

Sent back to MGID

Through the Conversion API or postback

Cost API

Spend pulled in

MGID cost matched to each campaign

Your ad

MGID click

Macros fill the tracking URL

ClickFlare

Click recorded

Zone, site and device data stored

Offer or lander

Visitor converts

On your page or the offer

ClickFlare

Conversion logged

With payout and event type

Postback

Reported to MGID

So its optimization sees the result

Your ad

Visitor clicks

Any traffic source

ClickFlare

Click recorded

A unique cf_click_id is created

Your article

Keyword block

Click ID passed to the feed

Results page

Paid click

Conversion fired to ClickFlare

MGID API

Revenue matched

Pulled on a schedule and reconciled

Your ad

Visitor clicks

Any traffic source

ClickFlare

Click recorded

cf_click_id passed to the offer

MGID

Offer or call

The network tracks the action

MGID

Conversion

Lead, sale, call or rebill

Postback

Payout in ClickFlare

Matched to the original click

Your ad

Visitor clicks

Any traffic source

ClickFlare

Click recorded

A unique cf_click_id is created

MGID

Store or funnel

Click ID kept through checkout

Events

View, cart, checkout

Each step tracked

ClickFlare

Purchase recorded

Order value matched to the ad

Native ad network

Client ID and goal name: the two values you replace

The postback URL MGID gives you holds your client ID after /postback/ and the goal name in e. Put both into the ClickFlare template. ClickFlare then sends the stored click ID in c and the payout in r.

A main goal plus two additional goals
Unique or non-unique counting per goal
Test clicks come from the ad preview

Today, one campaign

example

Spend pulled from MGID

cost

$412.30

Conversions recorded

today

Sent back to MGID

per event

38/38

Profit

campaign

$227.70

Example numbers. Cost and conversions sit in the same report row.

Captured on every MGID click

key macros

click_id, click_price, teaser_id, widget_id, campaign_id

captured

From the MGID template in ClickFlare. Use them as report columns and rules.

Revenue for one click

example

Paid click

day 0

$0.00

First revenue pull

+1h

$0.41

Scheduled updates

next days

$0.58

Final pull

last sync

$0.62

Example amounts. Sync timing for MGID is in the facts above.

Events for one click

example

Lead

day 0

$0.00

Sale

day 0

+$40.00

Upsell

day 1

+$15.00

Refund

day 9

−$15.00

Example events. Each one arrives by postback and is matched to the click.

One visitor's path

example

Product view

step 1

—

Add to cart

step 2

—

Checkout

step 3

—

Purchase

step 4

$68.00

Example order. Each event is tied to the ad that brought the visitor.

Goals per campaign

Tracking fields captured

2.3B

Events tracked

Setup

Connected in four steps

You need an MGID account with a conversion goal, your MGID email, password, Client API ID and access token for cost, and a ClickFlare account.

Add a goal in MGID In the MGID campaign, open Conversion tracking, choose Postback on the Tracking settings tab and add a goal such as purchase. Click Get Postback URL and note the client ID and goal name.
Add the MGID traffic source In the campaign editor, add a traffic source from the MGID template and set Cost currency to your MGID currency. Turn on the postback and replace YOUR_CLIENT_ID and REPLACE_EVENT_NAME.
Launch and test Paste the campaign URL into each MGID ad, with click_id appearing only once. Click the ad from MGID's preview, convert, and check the Test conversions column after 5 to 15 minutes.
Pull actual spend Add the MGID cost integration with your email, password, Client API ID, access token and a matching timezone. Select it on the traffic source and keep Cost Model on Not Tracked.

MGID postback from the ClickFlare template

https://a.mgid.com/postback/YOUR_CLIENT_ID?c={external_id}&e=REPLACE_EVENT_NAME&r={payout}

app.clickflare.com/integrations

MGID

Native ad network

Connected

MGID account connected

Signed in from ClickFlare

Cost syncing

Spend matched to campaigns

Conversions sent back

Your chosen events

MGID template selected

Macros pre-filled

Tracking URL in MGID

Click ID captured

Conversions reported

Payout included where supported

MGID connected

Credentials saved in ClickFlare

Conversion event set

Click ID passed to the feed

Revenue syncing

On the feed's schedule

MGID added

Offer URL carries the click ID

Postback set in MGID

Payout and event included

Conversions arriving

Matched to the click

MGID connected

Click ID kept to checkout

Events mapped

View, cart, checkout, purchase

Purchases tracked

Order value in reports

Ready to track

MGID's geo macro repeats your campaign targeting, not the visitor's country. Use ClickFlare's own geo data to see where visitors are.

MGID cost integration guide

Open the guide

In your reports

What you see once it's connected

ROI by widget
Results by teaser and title
Results by category
Cost per click
Results by referrer URL
Cost by campaign and content

Use cases

How media buyers run it

MGID → lander → offer

Send lead and purchase to two MGID goals, each with its own postback, and let MGID optimize on the sale.

MGID → article → RSOC

Feed revenue comes in hours or days later. Pass it to MGID with a delayed revenue postback once it arrives.

Widget blacklists

Group by widget_id, find placements with cost but no revenue, and block them in MGID.

Frequently asked questions

Questions about MGID

No items found.

Related integrations

More templates that plug into the same ClickFlare account.

MGo

MediaGo

Baidu's native ad platform

Native ad network

Outbrain

Native ads, now part of Teads

Native ad network

Revcontent

Native content discovery network

Native ad network

Taboola

Native advertising platform

Native ad network

AppLovin

Ad platform with a Conversion API

Ad platform

BIGO Ads

In-app ads on BIGO apps and network

In-app ad network

Browse all integrations ->

Setup guides

MGID cost integration guide

MGID postback setup guide

{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with MGID?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. ClickFlare has an MGID traffic source template with an S2S postback and per-click cost, plus a cost integration that pulls spend from MGID's API."}}, {"@type": "Question", "name": "How many conversion goals can I send to MGID?", "acceptedAnswer": {"@type": "Answer", "text": "Up to three per campaign: a main goal and two additional ones. Each goal needs its own postback with its name in e."}}, {"@type": "Question", "name": "Why click_id in the URL and c in the postback?", "acceptedAnswer": {"@type": "Answer", "text": "They carry the same value. ClickFlare reads MGID's click ID from click_id, and MGID expects it back in c. Change neither."}}, {"@type": "Question", "name": "Why doesn't my cost match MGID?", "acceptedAnswer": {"@type": "Answer", "text": "click_price is an estimate and doesn't account for clicks MGID discounts later. Connect the MGID cost integration and match its timezone to your account."}}, {"@type": "Question", "name": "Do I keep the click_price row if I use the cost integration?", "acceptedAnswer": {"@type": "Answer", "text": "There's no harm in keeping it. With Cost Model on Not Tracked, the integration takes priority. If you disconnect it, the URL cost takes over again."}}, {"@type": "Question", "name": "Can I rename my MGID goals later?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, but update the e value in the ClickFlare postback at the same time, or it stops matching."}}]}

MGID teasers and widgets,measured on revenue

Cut MGID widgets that cost more than they pay

Widget-level decisions

Cost from the first click

Exact spend when it matters

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

Client ID and goal name: the two values you replace

Connected in four steps

What you see once it's connected

How media buyers run it

MGID → lander → offer

MGID → article → RSOC

Widget blacklists

Questions about MGID

Related integrations

Your MGID campaigns, tracked widget by widget.