AdOperator feeds,whitelisted on real conversions

ClickFlare's AdOperator template captures AdOperator's click ID plus campaign, publisher sub ID, user agent, OS, browser and country on each click. Conversions go back through AdOperator's global S2S postback with the payout, so AdOperator's reports and yours agree.

Start for free

Read the setup guide

AdOperator

Self-serve popunder and push network

At a glance

How it connects

Template with click macros + global S2S postback

What syncs

Click ID, campaign, publisher sub ID, OS, browser, country

Sync schedule

Real time, per conversion

Key parameters

{conversion}, {campaign}, {subid}, {os}, {browser}

Works with

Popunder, push notifications, in-page push

Good to know

No cost in the template. Use CPC with your bid.

Push & pop network

Global postback

7 macros captured

Sort AdOperator publisher feeds by profit

Sub ID reports

Publisher sub ID carries the feed that sent the click. Group by it to see which feeds convert and blacklist or whitelist them in AdOperator.

One postback for every campaign

AdOperator's postback is global. The click ID tells it which campaign converted, so one ClickFlare traffic source covers all your AdOperator campaigns.

Payout in AdOperator reports

The postback sends value={payout}, so the conversions in AdOperator's Reports carry the same revenue as ClickFlare.

How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

Your ad

Visitor clicks

Ad on AdOperator

ClickFlare

Click recorded

A unique cf_click_id is created

Your offer

Conversion

Lead, sale or custom event

ClickFlare

Sent back to AdOperator

Through the Conversion API or postback

Cost API

Spend pulled in

AdOperator cost matched to each campaign

Your ad

AdOperator 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 AdOperator

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

AdOperator 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

AdOperator

Offer or call

The network tracks the action

AdOperator

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

AdOperator

Store or funnel

Click ID kept through checkout

Events

View, cart, checkout

Each step tracked

ClickFlare

Purchase recorded

Order value matched to the ad

Push & pop network

AdOperator's click ID, sent back as c

AdOperator fills {conversion} into the campaign URL. ClickFlare stores it as the External ID. On conversion, ClickFlare calls s2s.adoperator.com with the stored ID in c and the payout in value.

conversion in the URL, c in the postback
value is read as USD
No event parameter: send one conversion

Today, one campaign

example

Spend pulled from AdOperator

cost

$412.30

Conversions recorded

today

Sent back to AdOperator

per event

38/38

Profit

campaign

$227.70

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

Captured on every AdOperator click

key macros

{conversion}, {campaign}, {subid}, {os}, {browser}

captured

From the AdOperator 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 AdOperator 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.

Macros in the template

$20

Minimum campaign budget

2.3B

Events tracked

Setup

Connected in four steps

You need a funded AdOperator advertiser account, a ClickFlare account with your own tracking domain, and an offer.

Add the AdOperator traffic source In the campaign editor, click + New Traffic Source and pick the AdOperator template. It fills the click ID and six tracking fields.
Turn on the postback Turn on Traffic source postback URL. It matches AdOperator's Conversion Tracking URL with {external_id} in place of AdOperator's macro, so nothing needs changing.
Finish the campaign with CPC cost Set the Cost Model to CPC and enter your bid: CPC for push and in-page push, CPV for popunder. Add lander and offer and copy the campaign URL.
Create the campaign in AdOperator Paste the campaign URL into Target Url, pick the format, set budget, bid and targeting, add creatives for push, and click Start Campaign.

AdOperator postback URL in ClickFlare

https://s2s.adoperator.com/conversion?c={external_id}&value={payout}

app.clickflare.com/integrations

AdOperator

Push & pop network

Connected

AdOperator account connected

Signed in from ClickFlare

Cost syncing

Spend matched to campaigns

Conversions sent back

Your chosen events

AdOperator template selected

Macros pre-filled

Tracking URL in AdOperator

Click ID captured

Conversions reported

Payout included where supported

AdOperator connected

Credentials saved in ClickFlare

Conversion event set

Click ID passed to the feed

Revenue syncing

On the feed's schedule

AdOperator added

Offer URL carries the click ID

Postback set in AdOperator

Payout and event included

Conversions arriving

Matched to the click

AdOperator connected

Click ID kept to checkout

Events mapped

View, cart, checkout, purchase

Purchases tracked

Order value in reports

Ready to track

Popunder bids are CPV. A CPV of 0.001 USD is a CPM of 1 USD, and a typo here overspends fast. Add the {bid} macro to check the real click price.

AdOperator postback setup guide

Open the guide

In your reports

What you see once it's connected

ROI by publisher sub ID
Conversions by campaign
OS breakdown
Browser splits
Country reports
User agent details

Use cases

How media buyers run it

Popunder → offer

Buy AdOperator popunder on CPV, enter the CPV as CPC in ClickFlare, and blacklist sub IDs that never convert.

Push → lander → offer

Run push with up to four creatives, link the lander CTA to the ClickFlare click URL, and whitelist the feeds that pay.

Lead and sale funnels

Track lead and purchase as custom conversions, and map the AdOperator postback to purchase only.

Frequently asked questions

Questions about AdOperator

No items found.

Related integrations

More templates that plug into the same ClickFlare account.

BidVertiser

Self-serve pop, push and native network

Push & pop network

EvaDav

Self-serve push and popunder network

Push & pop network

Galaksion

Self-serve push, pop and native network

Push & pop network

Noviclick

Self-serve pop and push network

Push & pop network

PlugRush

Self-serve CPV ad network

Push & pop network

PropellerAds

Self-serve pop and push ad network

Push & pop network

Browse all integrations ->

Setup guides

AdOperator postback setup guide

{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with AdOperator?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. ClickFlare has an AdOperator traffic source template with its click macros and an S2S postback to s2s.adoperator.com."}}, {"@type": "Question", "name": "How do I set up AdOperator postback tracking?", "acceptedAnswer": {"@type": "Answer", "text": "Turn on Traffic source postback URL on the AdOperator traffic source in ClickFlare. It sends {external_id} in c and {payout} in value, and needs no changes."}}, {"@type": "Question", "name": "Why is it conversion in the URL and c in the postback?", "acceptedAnswer": {"@type": "Answer", "text": "Both carry the same value. ClickFlare reads AdOperator's click ID from conversion, and AdOperator expects it back in c. Change neither."}}, {"@type": "Question", "name": "Do I need a goal ID in the AdOperator postback?", "acceptedAnswer": {"@type": "Answer", "text": "Not with the postback AdOperator shows today in Conversion Tracking. If your account shows a different URL, use it and keep {external_id} and {payout} as the tokens."}}, {"@type": "Question", "name": "Does ClickFlare pull my AdOperator spend automatically?", "acceptedAnswer": {"@type": "Answer", "text": "No. There is no AdOperator cost integration. Use the CPC cost model with your bid, and correct any gap with a manual cost upload."}}, {"@type": "Question", "name": "Why is the User agent column empty?", "acceptedAnswer": {"@type": "Answer", "text": "{user_agent} is not in AdOperator's published macro list, so it may not fill in. Remove the row or leave it."}}]}

AdOperator feeds,whitelisted on real conversions

Sort AdOperator publisher feeds by profit

Sub ID reports

One postback for every campaign

Payout in AdOperator reports

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

AdOperator's click ID, sent back as c

Connected in four steps

What you see once it's connected

How media buyers run it

Popunder → offer

Push → lander → offer

Lead and sale funnels

Questions about AdOperator

Related integrations

Your AdOperator campaigns, tracked to the feed.