Konnektive orders,and upsells, per ad

ClickFlare ties every Konnektive order and one-click upsell back to the ad click that brought the buyer. Konnektive CRM, now named Checkout Champ, sends each order server to server with its real total, so ad blockers don't hide sales.

KN
Konnektive
CRM for offers, now Checkout Champ

Konnektive integration at a glance

How it connects
Server-to-server postback from a Konnektive pixel
What syncs
Orders, order totals, upsells and buyer contact details
How fresh the data is
Real time, when the order is placed
What you can optimize
Ads, angles and sources by front-end and upsell revenue
Works with
Front-end sales and one-click upsells
Good to know
Rebills, renewals and refunds aren't sent to ClickFlare.
Direct-response CRM
Upsell revenue split
No checkout script

Konnektive orders, tied to every ad

Sales and upsells split

See front-end sales and upsells as separate conversion columns, each at its own value.

No script on the checkout

Orders are sent server to server. Nothing runs on the checkout pages, and ad blockers don't affect it.

Uses fields you already have

The click ID travels in Konnektive's own affiliate fields, so there's nothing to build beyond an affiliate profile.
How it works

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

01
Your ad
Visitor clicks
Ad on Konnektive
02
ClickFlare
Click recorded
Every click gets its own ID
03
Your offer
Conversion
Lead, sale or custom event
04
ClickFlare
Sent back to Konnektive
Through the Conversion API or postback
05
Cost API
Spend pulled in
Konnektive cost matched to each campaign
01
Your ad
Konnektive 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 Konnektive
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
Konnektive 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
Konnektive
Offer or call
The network tracks the action
04
Konnektive
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
Konnektive
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
Konnektive
Lead or call stored
The ad stays linked to the lead
04
Konnektive
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
Konnektive
Your workflow
Rules, apps or an AI assistant
04
Konnektive
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
Konnektive
Data lands
Tables refreshed on schedule
05
Konnektive
Dashboards
Blended with your other data
Direct-response CRM

Orders sent from Konnektive to ClickFlare

Your ClickFlare link passes the click ID into the Konnektive checkout, which stores it with the order. When the order is placed, Konnektive sends it back with the order total, so each sale and upsell lands on its ad.
  • Click ID stored with each Konnektive order
  • One pixel per Konnektive campaign
  • Each upsell reported at its own value
Today, one campaign
example
Spend pulled from Konnektive
cost
$412.30
Conversions recorded
today
38
Sent back to Konnektive
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 Konnektive 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
Konnektive
3
Example numbers. You choose the breakdowns, date range and schedule.
One event, end to end
example
Conversion recorded
event
sent
Event delivered
Konnektive
received
Workflow ran
Konnektive
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 Konnektive (Checkout Champ) access to affiliates and campaigns, your own tracking domain and a ClickFlare account.
  1. Add the Checkout Champ template Pick the Checkout Champ template in ClickFlare with your own tracking domain. It fills in the order data for you.
  2. Build the offer and campaign Add your Konnektive checkout as the offer and create a campaign with your traffic source and an optional lander.
  3. Add a pixel in Konnektive Create an affiliate profile and add a ClickFlare pixel to each Konnektive campaign. Orders then land on the ad that drove them.
app.clickflare.com/integrations
KN
Konnektive
Direct-response CRM
Connected
Konnektive account connected
Signed in from ClickFlare
Cost syncing
Spend matched to campaigns
Conversions sent back
Your chosen events
Konnektive template selected
Macros pre-filled
Tracking URL in Konnektive
Click ID captured
Conversions reported
Payout included where supported
Konnektive connected
Credentials saved in ClickFlare
Conversion event set
Click ID passed to the feed
Revenue syncing
On the feed's schedule
Konnektive added
Offer URL carries the click ID
Postback set in Konnektive
Payout and event included
Conversions arriving
Matched to the click
Konnektive connected
Click ID kept to checkout
Events mapped
View, cart, checkout, purchase
Purchases tracked
Order value in reports
Click ID stored in Konnektive
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
Konnektive 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
Running upsells? Report each one at its own value as a separate conversion, so ClickFlare doesn't treat it as a repeat of the sale.
Konnektive setup guide
Open the guide
In your reports

What you see once it's connected

  • Sales per campaign
  • Upsell revenue per ad
  • Order value by traffic source
  • Sales vs. upsells
  • Revenue by lander
  • ROI by campaign
Use cases

How media buyers run it

Meta or TikTok → presell page → Konnektive checkout

Meta → presell → checkout

The lander passes the click ID on, so each order ties back to its ad.
Taboola or Outbrain → advertorial → checkout

Native → advertorial → offer

Compare placements by front-end plus upsell revenue.

Several Konnektive campaigns

Use one affiliate profile across your Konnektive campaigns, with a pixel on each, and see every order in ClickFlare.
Frequently asked questions

Konnektive integration FAQ

Does ClickFlare integrate with Konnektive?

Yes. Konnektive CRM, now named Checkout Champ, sends each order to ClickFlare server to server from a pixel on your affiliate profile, with the order total as revenue.

Is Konnektive the same as Checkout Champ?

Yes. Konnektive CRM was renamed Checkout Champ. The setup works the same way in both, and you use ClickFlare's Checkout Champ template.

Can I see upsells separately?

Yes. Each accepted upsell reports at its own value as its own conversion, so you see front-end and upsell revenue per ad without double counting.

Are rebills and renewals tracked?

Not by this setup. The pixel fires when the order is placed on the funnel pages. Rebills are charged later with no visitor on the page, so they don't trigger it.

Are refunds removed from ClickFlare?

No. The pixel only reports new orders. Refunds stay in Konnektive.

Why do conversions arrive without a campaign?

The order came back without a usable click ID. Usually the offer link isn't passing it, or the affiliate profile isn't set to keep it.

No items found.
Setup guides
Konnektive setup guide
Tracking conversions with an S2S postback
{"@context": "https://schema.org", "@graph": [{"@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with Konnektive?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Konnektive CRM, now named Checkout Champ, sends each order to ClickFlare server to server from a pixel on your affiliate profile, with the order total as revenue."}}, {"@type": "Question", "name": "Is Konnektive the same as Checkout Champ?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Konnektive CRM was renamed Checkout Champ. The setup works the same way in both, and you use ClickFlare's Checkout Champ template."}}, {"@type": "Question", "name": "Can I see upsells separately?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Each accepted upsell reports at its own value as its own conversion, so you see front-end and upsell revenue per ad without double counting."}}, {"@type": "Question", "name": "Are rebills and renewals tracked?", "acceptedAnswer": {"@type": "Answer", "text": "Not by this setup. The pixel fires when the order is placed on the funnel pages. Rebills are charged later with no visitor on the page, so they don't trigger it."}}, {"@type": "Question", "name": "Are refunds removed from ClickFlare?", "acceptedAnswer": {"@type": "Answer", "text": "No. The pixel only reports new orders. Refunds stay in Konnektive."}}, {"@type": "Question", "name": "Why do conversions arrive without a campaign?", "acceptedAnswer": {"@type": "Answer", "text": "The order came back without a usable click ID. Usually the offer link isn't passing it, or the affiliate profile isn't set to keep it."}}], "dateModified": "2026-11-12"}, {"@type": "BreadcrumbList", "itemListElement": [{"@type": "ListItem", "position": 1, "name": "Integrations", "item": "https://www.clickflare.com/integrations"}, {"@type": "ListItem", "position": 2, "name": "CRMs & Call Tracking", "item": "https://www.clickflare.com/integrations/crms-call-tracking"}, {"@type": "ListItem", "position": 3, "name": "Konnektive"}]}]}