Black Friday came early.Early-access pricesuntil Nov 8.Black Friday: early-access prices until Nov 8.Early-access price ends in0d00h00m00sClaim the deal
ClickFlare reads Kayzen's bid ID and 9 macros, including exchange, publisher app and device, from the campaign URL. Conversions go to Kayzen's Event API by S2S postback with your API key, the event name and revenue, so Kayzen optimizes on the events you choose.
In-app image, native, video and HTML ads across exchanges
Good to know
Each app or website has its own API key and traffic source
Mobile DSP
Kayzen Event API
9 macros captured
Bid on Kayzen inventory that converts
Exchange and app performance
{EXCHANGE_NAME} and {APP_NAME} land in every report. See which exchanges and publisher apps convert, then block or bid up inventory in Kayzen.
Named events for optimization
Each postback sends an app_event name, such as registration or purchase. Kayzen reports and optimizes on the exact name you send.
Revenue in any currency
Add revenue_USD={payout}, or revenue={payout} with currency={payout_currency}, so Kayzen sees the value of each event next to its spend.
How it works
From ad click to profit per campaignattributed revenueattributed salesa matched conversion
01
Your ad
Visitor clicks
Ad on Kayzen
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 Kayzen
Through the Conversion API or postback
05
Cost API
Spend pulled in
Kayzen cost matched to each campaign
01
Your ad
Kayzen 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 Kayzen
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
Kayzen 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
Kayzen
Offer or call
The network tracks the action
04
Kayzen
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
Kayzen
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
Mobile DSP
Bid ID in, Event API call out
Kayzen fills {CONVERSION_ID} in bid_id and ClickFlare stores it as the External ID. On conversion, ClickFlare calls api-events.kayzen.io with your API key, the event name, can_claim=1 and the bid ID.
can_claim=1 marks the event as a Kayzen click
One postback per app_event name
HTML creatives need {HTML_CLICK_URL}
Today, one campaign
example
Spend pulled from Kayzen
cost
$412.30
Conversions recorded
today
38
Sent back to Kayzen
per event
38/38
Profit
campaign
$227.70
Example numbers. Cost and conversions sit in the same report row.
From the Kayzen 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 Kayzen 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.
9
Tracking macros captured
2.3B
Events tracked
Setup
Connected in four steps
You need a Kayzen account with Admin Console access for the API key, a ClickFlare offer that posts conversions back, and your own tracking domain.
Copy your Event API key In Kayzen, click your name, choose Switch to Admin Console and open the app or website under App/Website. Copy the API Key from the event API integration details.
Create the Kayzen traffic source In a new campaign, click + New Traffic Source and pick the Kayzen template. It fills bid_id={CONVERSION_ID} and 9 macros for campaign, creative, exchange, app and device.
Finish the postback Turn on Traffic source postback URL. Replace Website_API_key and name_of_the_event, then add &revenue_USD={payout}. Keep tp=direct and can_claim=1.
Launch with Redirect tracking Set Cost Model to CPC and pick Redirect. Paste the campaign URL as Kayzen's click URL, then check Logs → Postback Status for a real bid_id and the event in Kayzen.
{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with Kayzen?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. ClickFlare's Kayzen template captures the bid ID and 9 macros, and sends conversions to Kayzen's Event API by S2S postback."}}, {"@type": "Question", "name": "Where do I find my Kayzen API key?", "acceptedAnswer": {"@type": "Answer", "text": "Switch to Admin Console, open the App/Website section, click the app or website you promote and copy the API Key at the bottom of the event API integration details."}}, {"@type": "Question", "name": "What does can_claim=1 do?", "acceptedAnswer": {"@type": "Answer", "text": "It tells Kayzen the event is attributed to a Kayzen click. Kayzen's default is 0, an unattributed event. Keep 1."}}, {"@type": "Question", "name": "How do I track Kayzen cost?", "acceptedAnswer": {"@type": "Answer", "text": "The template passes no cost. Set the Cost Model to CPC with your Kayzen spend divided by Kayzen clicks. A CPM bid divided by 1,000 doesn't work on in-app inventory."}}, {"@type": "Question", "name": "Should I use Redirect or Direct tracking with Kayzen?", "acceptedAnswer": {"@type": "Answer", "text": "Redirect. Kayzen sends users to your click URL after it records the click, so the campaign URL must be a ClickFlare redirect."}}, {"@type": "Question", "name": "Kayzen's docs show api-events.eventstracker.io. Which host do I use?", "acceptedAnswer": {"@type": "Answer", "text": "Keep the template's api-events.kayzen.io, which Kayzen's tracker integration guides use. If Kayzen's team gives you the other host, use theirs. The parameters are the same."}}]}
Your Kayzen campaigns, tracked to the payout.
Exchange, app and device ROI, with events sent back to Kayzen. Free 14-day trial, no credit card, free migration from any tracker.