BIGO Ads tracking tokens & macros
A tagged BIGO Ads destination URL looks like yoursite.com/landing?camp=__CAMPAIGN_ID__&channel=__PUBLISHER_ID__&adgroup=__AD_GROUP_ID__&ad=__AD_ID__. Four macros cover the campaign, the channel, the ad group and the ad. BIGO fills them at click time, and ValidVisit reads them on arrival, so every visit is attributed to the channel it ran on, then judged Valid or Invalid, with its evidence.
Cross-check any macro against the network’s official documentation. BIGO Ads official docs →
BIGO macros are written in capitals between double underscores. BIGO's table describes __PUBLISHER_ID__ as the channel ID for the advertising placement, and the placements BIGO offers are imo, Likee and BIGO Audience Network. It's the finest placement level BIGO passes: there is no app, site or sub-placement macro. __CAMPAIGN_ID__ identifies the campaign, and __CAMPAIGN_NAME__ gives its readable name. __AD_GROUP_ID__ and __AD_ID__ add the ad group and the ad.
BIGO's macro table has no macro named for a click ID. Its attribution identifier is __BBG__, the bbg value BIGO's own Events API needs to credit a conversion; BIGO warns that a truncated bbg is rejected, so leave that parameter alone if it's on your URL. ValidVisit ties each conversion to the visit itself rather than to a network click ID. Placement control in BIGO sits at ad-group level, where you can uncheck a media under Placement, so the useful habit is one channel per ad group. Then __AD_GROUP_ID__ and __PUBLISHER_ID__ point at the same switch, and a channel whose visits run largely Invalid is one you can turn off for that ad group. ValidVisit doesn't change your BIGO campaign; the placement settings are yours.
BIGO Ads macro → ValidVisit param
| Token | BIGO Ads macro | ValidVisit param | Example |
|---|---|---|---|
| Campaign ID *campaign | __CAMPAIGN_ID__ | vv_campaign_id | 123456 |
| Campaign Namecampaign | __CAMPAIGN_NAME__ | vv_campaign_name | 123456 |
| Channel (publisher) IDpublisher | __PUBLISHER_ID__ | vv_publisher_id | likee |
| Ad Group IDadset | __AD_GROUP_ID__ | vv_adset_id | 456789 |
| Ad IDad | __AD_ID__ | vv_ad_id | 789012 |
| Attribution ID (bbg)click | __BBG__ | vv_click_id | bbg_abc123 |
- BIGO Ads macro
__CAMPAIGN_ID__- ValidVisit param
vv_campaign_id- Example
- 123456
- BIGO Ads macro
__CAMPAIGN_NAME__- ValidVisit param
vv_campaign_name- Example
- 123456
- BIGO Ads macro
__PUBLISHER_ID__- ValidVisit param
vv_publisher_id- Example
- likee
- BIGO Ads macro
__AD_GROUP_ID__- ValidVisit param
vv_adset_id- Example
- 456789
- BIGO Ads macro
__AD_ID__- ValidVisit param
vv_ad_id- Example
- 789012
- BIGO Ads macro
__BBG__- ValidVisit param
vv_click_id- Example
- bbg_abc123
* required for BIGO Ads attribution.
Ready-to-use BIGO Ads tracking URL
https://yoursite.com/landing?utm_source=bigo-ads&utm_medium=social&vv_campaign_id=__CAMPAIGN_ID__&vv_campaign_name=__CAMPAIGN_NAME__&vv_publisher_id=__PUBLISHER_ID__&vv_adset_id=__AD_GROUP_ID__&vv_ad_id=__AD_ID__&vv_click_id=__BBG__Append these params to your landing-page URL — BIGO Ads fills the macros at click time, so every visit arrives attributed and ready to judge. No funnel hop.
See which BIGO Ads sources send bots.
- Every visit judged Valid or Invalid, worst source first.
- Attributed through the BIGO Ads tokens above, down to the placement.
- Works beside your tracker, with nothing added to the click path.
What BIGO Ads tokens let you break bots down by
- Channel (publisher) ID — The channel ID for the advertising placement: BIGO's own apps or the audience network.
Carries a per-click id, stored with each visit so a verdict traces back to the click.
- IP exclusionnot offered
- Device targetingnot offered
- OS targetingdocumented
- Browser targetingnot offered
- Connection typedocumented
- Languagedocumented
Tokens last verified against BIGO Ads’s docs on 2026-10-02.
The buyer unchecks entire medias under Placement (imo, Likee or BIGO Audience Network), and ads stop showing there — there is no documented field to paste a list of bad site/app/sub-source IDs, so a bad-source list can only justify turning off a whole channel (or excluding an uploaded GAID/IDFA list, created under Library > Audience > Create a Custom Audience > Customer File, in the ad group’s Include/Exclude Audience setting).
BIGO Ads tracking token FAQs
Which BIGO macro names the placement?+
__PUBLISHER_ID__, the channel the ad ran on. BIGO passes nothing finer, so the channel is the level ValidVisit's invalid share works at.
Does BIGO have a click ID macro?+
Not under that name. BIGO's table lists __BBG__, its ad attribution identifier, which BIGO's own Events API matches conversions on. ValidVisit identifies each visit itself, so the verdicts don't depend on a network click ID; __CAMPAIGN_ID__ is the macro to always include.
Can I exclude a bad site or app on BIGO?+
Not by ID. BIGO documents no field for pasting site, app or sub-source IDs; placement control means turning whole channels on or off per ad group. A high invalid share on one channel is a reason to uncheck it for that ad group.
Which targeting controls does BIGO Ads offer?+
BIGO documents operating system, OS version, language, carrier, connection type and device price targeting. It documents no IP exclusion and no browser targeting, so channel and ad-group choices are the main levers, and once you've uploaded a GAID list you can exclude that audience in the ad group.
Tracking tokens for other social networks
Judge every BIGO Ads visit — and find the fake ones.
See which BIGO Ads publishers and placements send real buyers vs. bots.
Join the waitlist with just your email · 7-day trial at launch
One script · no cookies · no device IDs · raw IP never stored