MGID widget blacklist: how to decide which widgets to cut and when
MGID widget blacklist: how to decide which widgets to cut and when
An MGID widget blacklist is a list of widget IDs you stop buying traffic from because your own tracker data shows they lose money. You build it by passing MGID's widget token into a sub-ID, recording conversions by postback, and then reading cost and revenue per widget inside your tracker rather than inside MGID's interface. The decision to cut a widget is a threshold decision, not a gut feeling: you need enough clicks and enough conversions to know the widget is bad, not just unlucky. This guide covers the exact mechanics — which token to use, how to read the report, what sample size to wait for, and when to keep a widget that looks bad but isn't.
What is an MGID widget, and why do widgets need a blacklist at all?
MGID buys traffic from publishers who embed MGID's ad units — widgets — on their pages. Each widget has its own ID, and each widget's audience behaves differently. One widget might sit on a legitimate news site and send engaged readers. Another might sit below the fold on a made-for-advertising page where the click is the only thing the visitor ever does.
MGID lets you exclude widgets at the campaign level, but the exclusion only works if you know which widgets to exclude. MGID's own reporting shows you clicks and spend per widget; it cannot show you which widget produced a paid conversion, because the conversion happens on your offer page, after the click. That gap is the entire reason you need a tracker in the middle.
If you skip the tracker step, you end up blacklisting on click quality heuristics — bounce rate, time on page, MGID's own engagement signals. Those are proxies. They correlate with performance sometimes and lie to you other times. A widget with terrible engagement can still convert if your offer matches its audience; a widget with beautiful engagement can send thousands of clicks that never buy.
Step 1: pass the MGID widget ID into a sub-ID
Before you can blacklist anything, you need the widget ID attached to every click and every conversion. MGID exposes placement-level tokens in its campaign URL builder. The one you want is the widget identifier — MGID documents it as {widget_id} in the tracking URL template, alongside teaser and campaign tokens.
The pattern is the same one used across native networks: take MGID's macro, place it in the destination URL as the value of one of your tracker's sub-ID parameters, and let the tracker record it against the click.
- In MGID, open your campaign's tracking settings and add
{widget_id}to the destination URL assub1={widget_id}(or whichever sub-ID slot you've reserved for widget). - Reserve your sub-ID slots deliberately. A workable convention:
sub1= widget ID,sub2= teaser/creative ID,sub3= campaign ID. Write this down; you will forget. - Save the campaign and let it run. Every click now arrives at your tracker carrying the widget ID.
- Confirm the parameter is landing by opening a click log entry and checking that
sub1contains a numeric widget value, not the literal string{widget_id}. If you see the brace text, the macro wasn't substituted and your URL is malformed.
If you're setting this up for the first time, the full walkthrough is in MGID tracking setup: passing widget and teaser IDs into your tracker, and the general macro logic is covered in Ad network tracking macros explained: what tokens are and how to map them to sub-IDs.
Note that sub-ID pass-through and postback conversion tracking are Adtraxo Pro features. On the Free plan you can still run links and see click stats, but you cannot attribute revenue per widget, which means you cannot build a data-driven widget blacklist. That's a hard limitation, not a marketing nudge — per-placement profitability requires per-placement conversions.
Step 2: send conversions back by postback so each widget carries revenue
Clicks per widget are easy. Revenue per widget is the part most affiliates get wrong, because they read conversion counts inside the affiliate network and try to eyeball a match against MGID's widget report. That comparison is manual, slow, and breaks the moment you run two campaigns at once.
The fix is a server-to-server postback. Your affiliate network or offer platform fires a postback to your tracker when a conversion is confirmed, and the tracker matches it to the original click using the click ID it stored — which already carries the widget ID in sub1. From that point, every conversion is permanently attached to a widget.
- In your tracker, create a conversion goal and copy its postback URL.
- In your affiliate network, paste that URL into the postback/conversion pixel field, using the network's click ID macro in the slot your tracker expects.
- Fire a test conversion (most networks have a test button, or use a $0 test offer) and confirm it appears in the tracker with the correct
sub1value attached. - Check the timestamp and the click ID match. A postback that arrives but doesn't match a stored click is worse than no postback — it silently drops revenue.
If you're running Taboola alongside MGID, the postback mechanics are identical but the token names differ; see Taboola conversion tracking for affiliates: sending sales back with a postback for the comparison.
Step 3: read cost and revenue per widget in one report
Now the report that matters: for each widget ID, cost, clicks, conversions, revenue, and profit. In Adtraxo this is the per-campaign breakdown with the sub-ID dimension — you filter by sub1 and get one row per widget, with the conversion count and revenue already joined to the spend you imported or configured.
Two things to check before you trust any row:
- Click discrepancy. If MGID reports 4,000 clicks to a widget and your tracker recorded 3,100, your cost-per-click math is wrong and every profit figure derived from it is wrong. Discrepancies usually come from redirect chains, slow landing pages, or bot traffic that never executed the tracker. See Why your ad network and your tracker show different click counts.
- Conversion lag. Native conversions often arrive hours or days after the click. A widget that looks like a zero-conversion loser at hour six may be your best performer by day three. Never blacklist inside the conversion window of your offer.
Sort the report by spend descending, not by profit. The widgets burning the most money are the ones worth investigating first; a widget that spent $3 and lost $2 is noise, not a finding.
How many clicks before you can blacklist a widget?
There is no universal number, and anyone who gives you one is guessing. What you can do is reason from your own economics.
Work out your break-even conversion rate: if your average payout is $20 and your average CPC on MGID is $0.05, you break even at one conversion per 400 clicks. To be reasonably confident a widget is below break-even rather than just cold, you want to see it accumulate several times that click volume with zero or near-zero conversions. At 400 clicks you have a coin flip; at 1,200–2,000 clicks with no conversions, the probability that the widget is actually at break-even or better gets small enough to act on.
A practical rule that holds up across accounts:
- Under 1× break-even clicks, no conversions: do nothing. You don't have data.
- 1–3× break-even clicks, no conversions: flag it, don't cut it. Watch it for another day.
- 3× break-even clicks or more, zero conversions: blacklist. This is your core signal.
- Any volume, conversions present but ROI deeply negative: blacklist only if the loss per conversion is large enough that even a modest improvement wouldn't save it. A widget converting at 0.4× target ROI might respond to a bid cut; a widget converting at 0.1× will not.
- Conversions present and ROI positive: never blacklist, regardless of how ugly the click quality looks.
This is the same logic used for building a PropellerAds zone blacklist from your own tracker data — different network, identical decision framework, because the underlying statistics don't care which ad platform you're buying.
When to cut a widget vs. when to fix it
Blacklisting is destructive: once a widget is out, you stop collecting data on it and you can't easily tell whether it would have recovered. Before you cut, run through these checks in order.
Is the widget's traffic the problem, or your creative?
If a widget has a 0.05% CTR but the clicks that do arrive convert at target, the widget isn't bad — your teaser isn't matching its audience. Test a different teaser on that widget before you blacklist it. Compare creatives by conversions rather than clicks, as covered in Push ad creative testing: how to compare creatives by conversions, not clicks.
Is the widget's traffic the problem, or your landing page?
Geo and device breakdown will tell you. If a widget sends 90% Android in-app traffic and your landing page loads slowly on mobile, the widget is fine and your page is the leak. Adtraxo's per-campaign analytics break down by geo and device, so you can check this before cutting a widget that might be salvageable with a lighter page.
Is the widget fraudulent?
Some widget placements are simply bot traffic. Signs: click volume that arrives in unnatural bursts, datacenter IPs, identical user agents, or a click-to-conversion rate so low it's statistically implausible. Adtraxo's fraud detection flags IP velocity, datacenter IPs, bot user agents, uniqueness conflicts and invalid referers — if a widget's traffic trips several of those, blacklist on fraud grounds rather than performance grounds. You'll want it gone regardless of what the ROI report says.
Would a bid adjustment fix it?
If the widget converts but at a CPA above target, a lower bid may bring it back into profit. Try that before blacklisting. Widgets that convert at all are worth more to you than widgets that don't, because they've proven the audience responds.
Applying the blacklist inside MGID
Once you've decided, apply the exclusion at the campaign level in MGID's widget exclusion settings. Two operational notes:
- Blacklist per campaign, not globally, until you have repeat evidence. A widget that fails on a finance offer may work on a sweepstakes offer. Only promote a widget to a global exclusion list after it has failed across two or more unrelated campaigns.
- Keep a dated log. Record the widget ID, the campaign, the spend, the conversions, and the date you cut it. Six weeks later you'll want to know whether that widget was ever re-tested, and MGID's interface won't remember for you.
If you're also buying Taboola, the publisher-site equivalent of this process is in How to find and block the Taboola publisher sites that waste your budget, and the RichAds creative-level version is in RichAds tracking setup: postbacks and creative IDs for push campaigns. The network-by-network overview that ties all of these together is How to track native and push ad campaigns: a network-by-network setup guide.
Common mistakes that ruin a widget blacklist
- Blacklisting on clicks instead of conversions. High click volume with no conversions is a signal; low click volume is not. Always normalise by spend.
- Cutting inside the conversion window. Native offers with 24–72 hour lag will look like losers at the moment you check. Wait out the window.
- Trusting MGID's conversion column. MGID can only report what its pixel sees. If your conversion happens on a thank-you page MGID can't reach, MGID shows zero and your tracker shows the truth. Always use the tracker's number.
- Never re-testing. Widgets change hands, publishers change layouts, audiences shift. A widget you cut in March may be worth a fresh look in June — pull it from the blacklist on a new campaign and see.
- Blacklisting everything that isn't a star. The goal is to cut the losers, not to shrink your buy to three widgets. Keep the break-even performers; they're carrying volume while you find winners.
Frequently asked questions
What is an MGID widget blacklist?
It's a list of MGID widget IDs you exclude from your campaigns because your own tracker data shows they spend money without returning conversions or profit. You build it by passing MGID's {widget_id} token into a sub-ID and recording conversions by postback, then reading cost and revenue per widget in your tracker.
How many clicks do I need before blacklisting an MGID widget?
Enough to be confident the widget is below your break-even conversion rate. A practical rule: wait for at least three times the click volume your break-even rate implies, with zero conversions, before cutting. Below that, you're acting on noise. Also wait out your offer's full conversion lag window before deciding.
Should I blacklist a widget that converts but at a negative ROI?
Only if the loss is severe. A widget converting at a modestly negative ROI may respond to a lower bid and become profitable. A widget converting at a fraction of target ROI, or losing heavily per conversion, is worth cutting. Widgets that produce any conversions have proven audience response, which makes them more valuable than zero-conversion widgets.
Can I build an MGID widget blacklist without a tracker?
Not reliably. MGID reports clicks and spend per widget but cannot see conversions that happen on your offer page. Without a tracker joining click data to conversion data, you'd be blacklisting on engagement proxies rather than actual profit, which routinely cuts profitable widgets and keeps losing ones.
Does Adtraxo support MGID widget-level blacklisting?
Adtraxo records the widget ID you pass into a sub-ID (sub1–sub5, a Pro feature) and joins it to conversions received by S2S postback (also Pro), giving you cost, conversions and profit per widget in one report. You then apply the exclusion inside MGID. Pro is $27/month at the founding rate, with a 30-day money-back guarantee.
Ready to stop guessing which MGID widgets are eating your budget? Set up your first tracked MGID campaign at adtraxo.com and let your own conversion data build the blacklist.
Track your affiliate campaigns for free
Clicks, conversions, fraud detection — all in one tracker.
Get started free →Not ready for an account? Get the Tracking Domination Playbook — free, just your email.