CAKE conversions,with payout on every click

ClickFlare matches each conversion from a CAKE network to the click, campaign and traffic source behind it, with its payout, in real time. Each event counts on its own, and the same setup works on networks that run on CAKE.

CK
CAKE
Software behind many CPA networks

CAKE integration at a glance

How it connects
Server-to-server postback on each CAKE offer
What syncs
Conversions, events, payout and a lead ID per click
How fresh the data is
Real time, per conversion
What you can optimize
Sources, offers and networks by payout per event
Works with
Networks running on CAKE, including multi-event offers
Good to know
Rejected or scrubbed conversions aren't sent. Check network reports.
Affiliate network
Payout per event
Any CAKE network

Judge CAKE offers on real payouts

Same setup on every portal

ClickDealer, Advidi, Adeer, Gotzha, Yepads and many other networks run on CAKE. The same ClickFlare setup works on each.

Each event counted on its own

CAKE reports every published event, each with its own ID, so a lead and a later sale on one click both count.

Resends count once

If CAKE resends a conversion, it carries the same ID, so ClickFlare doesn't count it twice.
How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversionautomated actionyour dashboardsclosed revenue

01
Your ad
Visitor clicks
Ad on CAKE
02
ClickFlare
Click recorded
Every click gets its own ID
03
Your offer
Conversion
Lead, sale or custom event
04
ClickFlare
Sent back to CAKE
Through the Conversion API or postback
05
Cost API
Spend pulled in
CAKE cost matched to each campaign
01
Your ad
CAKE click
Placement, device and country come along
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 CAKE
So its optimization sees the result
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
Every click gets its own ID
03
Your article
Keyword block
Click ID passed to the feed
04
Results page
Paid click
Conversion fired to ClickFlare
05
CAKE API
Revenue matched
Pulled on a schedule and reconciled
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
The click follows the visitor to the offer
03
CAKE
Offer or call
The network tracks the action
04
CAKE
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
Every click gets its own ID
03
CAKE
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
01
Your ad
Visitor clicks
Form, call or landing page
02
ClickFlare
Click recorded
Every click gets its own ID
03
CAKE
Lead or call stored
The ad stays linked to the lead
04
CAKE
Qualified or closed
Workflow or call rule fires
05
ClickFlare
Revenue recorded
Tied to the ad that drove it
01
ClickFlare
Event happens
Click, conversion or custom event
02
Webhook or API
Data goes out
Or comes back in
03
CAKE
Your workflow
Rules, apps or an AI assistant
04
CAKE
Action
Alert, update, pause or scale
05
ClickFlare
Back in reports
Changes show in your data
01
ClickFlare
Report data
Campaigns, sources, offers
02
ClickFlare API
Your numbers go out
Secured with your API key
03
Your setup
Scheduled refresh
A sheet, script or connector
04
CAKE
Data lands
Tables refreshed on schedule
05
CAKE
Dashboards
Blended with your other data
Affiliate network

From CAKE conversion to ROI per source

ClickFlare passes its click ID on the CAKE offer link. When the visitor converts, CAKE reports the conversion with its payout and ID, and ClickFlare records it on the original click and source.
  • Conversions arrive as they happen
  • Each event counted as its own conversion
  • One affiliate network per CAKE network
Today, one campaign
example
Spend pulled from CAKE
cost
$412.30
Conversions recorded
today
38
Sent back to CAKE
per event
38/38
Profit
campaign
$227.70
Example numbers. Cost and conversions sit in the same report row.
ROI per placement
example
Placement A · mobile
cost
$38.20
Placement A
revenue
$71.40
Placement A
ROI
+87%
Placement B · desktop
ROI
−42%
Example numbers. Keep the placements that pay and cut the ones that lose money.
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 CAKE 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.
One lead, followed to revenue
example
Lead created
day 0
$0.00
Qualified
day 2
+$25.00
Deal closed
day 14
+$480.00
Renewal
day 45
+$120.00
Example values. Each stage can be its own event type in ClickFlare.
A scheduled report refresh
example
Campaigns
in the report
1,240 rows
Cost, revenue, profit
per campaign
included
Refresh
your schedule
done
Dashboards fed
CAKE
3
Example numbers. You choose the breakdowns, date range and schedule.
One event, end to end
example
Conversion recorded
event
sent
Event delivered
CAKE
received
Workflow ran
CAKE
done
Team notified
your apps
done
Example run. What happens after the event is up to your workflow.
2.3B
Events tracked
Setup

Connected in three steps

You need a ClickFlare account with your own tracking domain and an affiliate account on the network's CAKE portal, approved for the offer.
  1. Add the network from the template Pick the CAKE template in ClickFlare and name it after your network. It builds the postback for you.
  2. Add your approved offer Add the CAKE offer link to your campaign with the click ID toggle on, and let the payout come from the network.
  3. Add the postback on the offer Add the postback to the offer in the CAKE portal. Conversions then show per click, source and offer.
app.clickflare.com/integrations
CK
CAKE
Affiliate network
Connected
CAKE account connected
Signed in from ClickFlare
Cost syncing
Spend matched to campaigns
Conversions sent back
Your chosen events
CAKE template selected
Macros pre-filled
Tracking URL in CAKE
Click ID captured
Conversions reported
Payout included where supported
CAKE connected
Credentials saved in ClickFlare
Conversion event set
Click ID passed to the feed
Revenue syncing
On the feed's schedule
CAKE added
Offer URL carries the click ID
Postback set in CAKE
Payout and event included
Conversions arriving
Matched to the click
CAKE connected
Click ID kept to checkout
Events mapped
View, cart, checkout, purchase
Purchases tracked
Order value in reports
Click ID stored in CAKE
Hidden field or call data
Workflow or rule set
Fires on the stage you choose
Conversions arriving
With payout and event type
API key created
Settings, then Security
Report pull scheduled
Dimensions and date range set
CAKE dashboards live
Refreshed on schedule
Connection set up
Webhook, API key or MCP
Events chosen
Only what the workflow needs
Workflow running
Tested end to end
Ready to track
Postbacks are per offer. Only the network can place one for all offers, so send the postback to your affiliate manager if you want that.
CAKE setup guide
Open the guide
In your reports

What you see once it's connected

  • Conversions per offer
  • Payout per event
  • ROI by traffic source
  • Results per CAKE network
  • EPC per offer
  • Profit by country and device
Use cases

How media buyers run it

Native → lander → CAKE offer

Lead gen on CAKE networks

The lander links through ClickFlare, so each lead lands on its lander and placement.

Several CAKE networks side by side

Create one affiliate network per CAKE portal, such as "CAKE - ClickDealer", and compare networks on payout and ROI in one report.
Push → CAKE offer that pays on a lead and a sale

Multi-step offers

Each event arrives with its own ID and payout, so you see what each step earns.
Frequently asked questions

CAKE integration FAQ

Does ClickFlare integrate with CAKE?

Yes. ClickFlare has a CAKE template. The network's CAKE portal sends each conversion with its payout and ID back by server-to-server postback.

Does it work with every network on CAKE?

It works on networks that run on CAKE, such as ClickDealer, Advidi and Adeer. Create one affiliate network per portal and compare them in one report.

Will a lead and a later sale both count?

Yes. CAKE gives each conversion its own ID, so separate events stay separate and a resend counts once.

Does CAKE send rejected or scrubbed conversions?

No. CAKE doesn't tell affiliates when a conversion is approved or rejected. Compare against the network's report before payday and adjust in ClickFlare.

Can I set one postback for all CAKE offers?

Only the network can. Postbacks are per offer, so send the ClickFlare postback to your affiliate manager if you want one for all offers.

How do I test a CAKE postback?

Ask your affiliate manager to fire a test conversion on your click, or complete the offer if allowed. Don't rely on Test Mode alone: it can suppress affiliate pixels and pays 0.

No items found.
Setup guides
CAKE setup guide
Click ID and postback macros guide
{"@context": "https://schema.org", "@graph": [{"@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with CAKE?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. ClickFlare has a CAKE template. The network's CAKE portal sends each conversion with its payout and ID back by server-to-server postback."}}, {"@type": "Question", "name": "Does it work with every network on CAKE?", "acceptedAnswer": {"@type": "Answer", "text": "It works on networks that run on CAKE, such as ClickDealer, Advidi and Adeer. Create one affiliate network per portal and compare them in one report."}}, {"@type": "Question", "name": "Will a lead and a later sale both count?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. CAKE gives each conversion its own ID, so separate events stay separate and a resend counts once."}}, {"@type": "Question", "name": "Does CAKE send rejected or scrubbed conversions?", "acceptedAnswer": {"@type": "Answer", "text": "No. CAKE doesn't tell affiliates when a conversion is approved or rejected. Compare against the network's report before payday and adjust in ClickFlare."}}, {"@type": "Question", "name": "Can I set one postback for all CAKE offers?", "acceptedAnswer": {"@type": "Answer", "text": "Only the network can. Postbacks are per offer, so send the ClickFlare postback to your affiliate manager if you want one for all offers."}}, {"@type": "Question", "name": "How do I test a CAKE postback?", "acceptedAnswer": {"@type": "Answer", "text": "Ask your affiliate manager to fire a test conversion on your click, or complete the offer if allowed. Don't rely on Test Mode alone: it can suppress affiliate pixels and pays 0."}}], "dateModified": "2026-11-12"}, {"@type": "BreadcrumbList", "itemListElement": [{"@type": "ListItem", "position": 1, "name": "Integrations", "item": "https://www.clickflare.com/integrations"}, {"@type": "ListItem", "position": 2, "name": "Networks & Feeds", "item": "https://www.clickflare.com/integrations/networks-feeds"}, {"@type": "ListItem", "position": 3, "name": "CAKE"}]}]}