BIGO Ads in-app traffic,attributed to your pixel

The BIGO Ads template captures the __SID__ click ID, the __BBG__ attribution ID and account, ad group, ad and publisher macros. ClickFlare posts each conversion to BIGO's attribution endpoint with your Website Pixel ID, and the cost integration pulls spend through BIGO's API.

BG
BIGO Ads
In-app ads on BIGO apps and network
At a glance
How it connects
S2S postback + cost API (Client ID, Secret, Refresh Token)
What syncs
Conversion events out, campaign cost in
Sync schedule
Real time, per conversion
Key parameters
click_id, bbg, ad_group_id, ad_id, publisher_id
Works with
In-app ads on BIGO LIVE, Likee, imo and network apps
Good to know
The template sends the event only, with no payout
In-app ad network
Website Pixel postback
15 macros captured

BIGO web conversions that match the click

Attribution BIGO accepts

BIGO's Web Events API rejects events without a valid bbg. The template stores __BBG__ and sends it back with every conversion.

Apps and ad groups that convert

ad_group_id, ad_id and publisher_id show which ad groups, creatives and apps drive your conversions.

Test before you spend

BIGO's Test Pixel page shows Success when the postback lands, so you can confirm the setup before launch.
How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

01
Your ad
Visitor clicks
Ad on BIGO Ads
02
ClickFlare
Click recorded
A unique cf_click_id is created
03
Your offer
Conversion
Lead, sale or custom event
04
ClickFlare
Sent back to BIGO Ads
Through the Conversion API or postback
05
Cost API
Spend pulled in
BIGO Ads cost matched to each campaign
01
Your ad
BIGO Ads click
Macros fill the tracking URL
02
ClickFlare
Click recorded
Zone, site and device data stored
03
Offer or lander
Visitor converts
On your page or the offer
04
ClickFlare
Conversion logged
With payout and event type
05
Postback
Reported to BIGO Ads
So its optimization sees the result
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
A unique cf_click_id is created
03
Your article
Keyword block
Click ID passed to the feed
04
Results page
Paid click
Conversion fired to ClickFlare
05
BIGO Ads API
Revenue matched
Pulled on a schedule and reconciled
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
cf_click_id passed to the offer
03
BIGO Ads
Offer or call
The network tracks the action
04
BIGO Ads
Conversion
Lead, sale, call or rebill
05
Postback
Payout in ClickFlare
Matched to the original click
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
A unique cf_click_id is created
03
BIGO Ads
Store or funnel
Click ID kept through checkout
04
Events
View, cart, checkout
Each step tracked
05
ClickFlare
Purchase recorded
Order value matched to the ad
In-app ad network

SID and BBG in, Website Pixel event out

BIGO fills click_id with __SID__ and bbg with __BBG__ when the ad is clicked. On a conversion, ClickFlare sends both back with your pixel ID and the event ID, button by default, which must match the ad group's optimization event.
  • appKey Clickflare_o9YVvj stays as it is
  • One postback per BIGO event ID
  • BBG stays on tracking field 15
Today, one campaign
example
Spend pulled from BIGO Ads
cost
$412.30
Conversions recorded
today
38
Sent back to BIGO Ads
per event
38/38
Profit
campaign
$227.70
Example numbers. Cost and conversions sit in the same report row.
Captured on every BIGO Ads click
key macros
click_id, bbg, ad_group_id, ad_id, publisher_id
captured
From the BIGO Ads 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 BIGO Ads 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.
15
Tracking fields captured
2.3B
Events tracked
Setup

Connected in four steps

You need a BIGO Ads account with a Website Pixel, a Client ID, Secret and Refresh Token from your BIGO account manager, and a ClickFlare account.
  1. Create a Website Pixel In BIGO Ads, go to Library → Website Pixel, create a pixel and copy its ID. For S2S tracking, BIGO's manual setup option is Bigo Pixel+Event_API.
  2. Add the BIGO Ads traffic source In the campaign editor, add a traffic source from the Bigo Ads template. Turn on Traffic source postback URL and replace REPLACE in pixel_id with your pixel ID.
  3. Launch with the pixel on Create a Conversions campaign in BIGO and paste the campaign URL as the landing page. Turn on the Website Pixel and choose the event that matches event_id, button by default.
  4. Pull BIGO cost Add the BIGO Ads cost integration with the Client ID, Secret, Refresh Token and a matching timezone. Select it on the traffic source and set the Cost Model to Not Tracked.
BIGO Ads postback from the ClickFlare template
https://attr.img-static.tech/attribution/apply/v2?sid={external_id}&appKey=Clickflare_o9YVvj&appId={trackingField1}&idfa={trackingField11}&gaid={trackingField12}&mappedIae=button&event_id=button&ad_ext={trackingField9}&pixel_id=REPLACE&bbg={trackingField15}
app.clickflare.com/integrations
BG
BIGO Ads
In-app ad network
Connected
BIGO Ads account connected
Signed in from ClickFlare
Cost syncing
Spend matched to campaigns
Conversions sent back
Your chosen events
BIGO Ads template selected
Macros pre-filled
Tracking URL in BIGO Ads
Click ID captured
Conversions reported
Payout included where supported
BIGO Ads connected
Credentials saved in ClickFlare
Conversion event set
Click ID passed to the feed
Revenue syncing
On the feed's schedule
BIGO Ads added
Offer URL carries the click ID
Postback set in BIGO Ads
Payout and event included
Conversions arriving
Matched to the click
BIGO Ads connected
Click ID kept to checkout
Events mapped
View, cart, checkout, purchase
Purchases tracked
Order value in reports
Ready to track
To send revenue, first ask your BIGO account manager whether this endpoint accepts monetary. The template doesn't send a payout.
BIGO Ads cost integration guide
Open the guide
In your reports

What you see once it's connected

  • Results by ad group
  • Results by ad
  • ROI by publisher app
  • Results by campaign
  • iOS vs Android
  • Results by account ID
Use cases

How media buyers run it

BIGO → lander → offer

Optimize the ad group on button or another standard web event, and send that event from ClickFlare when the offer converts.

Lead and purchase events

Send form for leads and ec_purchase for sales, one postback each, and optimize the ad group on the final one.

App placement pruning

Group by publisher_id to see which BIGO-owned or third-party apps convert, and cut the rest.
Frequently asked questions

Questions about BIGO Ads

No items found.
Setup guides
BIGO Ads cost integration guide
BIGO Ads postback setup guide
{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with BIGO Ads?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. ClickFlare has a BIGO Ads traffic source template that posts conversions to your Website Pixel, and a cost integration that pulls spend through BIGO's API."}}, {"@type": "Question", "name": "What is appKey=Clickflare_o9YVvj?", "acceptedAnswer": {"@type": "Answer", "text": "The channel key BIGO issued for ClickFlare. It tells BIGO which tracker sent the event and is the same for every ClickFlare user. Don't change it."}}, {"@type": "Question", "name": "Does the BIGO postback send revenue?", "acceptedAnswer": {"@type": "Answer", "text": "No. The template sends the event only. Ask your BIGO account manager whether you can add monetary={payout} before you rely on it."}}, {"@type": "Question", "name": "Why doesn't BIGO record my test event?", "acceptedAnswer": {"@type": "Answer", "text": "Check that REPLACE holds your pixel ID, the pixel is on in the ad group, bbg isn't empty, and the visit came through BIGO's test link."}}, {"@type": "Question", "name": "Why does the postback send IDFA and GAID on a web campaign?", "acceptedAnswer": {"@type": "Answer", "text": "BIGO's attribution endpoint also serves app campaigns, where those values are required. For web conversions, BIGO needs sid, bbg and pixel_id."}}]}