Glitchy offers,tracked from click to payout

Glitchy puts hundreds of offers in one platform. ClickFlare appends its click ID to each Glitchy offer as source={cf_click_id}, and Glitchy returns it in an offer-level postback with the payout, so every conversion lands on the right click.

GL
Glitchy
Offer aggregator and network hub
At a glance
How it connects
S2S postback set on each Glitchy offer
What syncs
Conversions and payouts
Sync schedule
Real time, per conversion
Key parameters
source={cf_click_id}, {source}, {payout}
Works with
Any Glitchy offer with any ClickFlare traffic source
Good to know
Set the postback per offer in Conversion Attribution Postback.
Affiliate network
Offer-level postback
Auto-appended click ID

Glitchy offers with payouts on every click

Many offers, one network setup

Add the Glitchy network once. Each new offer links to it, so you only paste the offer URL and set its postback.

Click ID appended for you

Toggle Append Click ID on the offer and ClickFlare adds source={cf_click_id} to the URL. No manual URL editing.

Payout on every conversion

The template postback includes {payout}, so ClickFlare logs revenue per conversion and shows ROI per campaign.
How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

01
Your ad
Visitor clicks
Ad on Glitchy
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 Glitchy
Through the Conversion API or postback
05
Cost API
Spend pulled in
Glitchy cost matched to each campaign
01
Your ad
Glitchy 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 Glitchy
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
Glitchy 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
Glitchy
Offer or call
The network tracks the action
04
Glitchy
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
Glitchy
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
Affiliate network

source out, {source} back

ClickFlare records the click and redirects to the Glitchy offer with source={cf_click_id} appended. When the visitor converts, Glitchy fires the ClickFlare postback for that offer, filling {source} with the click ID and {payout} with the revenue.
  • Template builds the postback URL
  • Postback set inside each Glitchy offer
  • Payout logged per conversion
Today, one campaign
example
Spend pulled from Glitchy
cost
$412.30
Conversions recorded
today
38
Sent back to Glitchy
per event
38/38
Profit
campaign
$227.70
Example numbers. Cost and conversions sit in the same report row.
Captured on every Glitchy click
key macros
source={cf_click_id}, {source}, {payout}
captured
From the Glitchy 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 Glitchy 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.
2.3B
Events tracked
Setup

Connected in four steps

You need an active Glitchy account, an active ClickFlare account and access to both platforms' postback settings.
  1. Add Glitchy from the template In ClickFlare, go to Affiliate Networks, click Add New Network and pick Glitchy. Copy the postback URL the template generates and save the network.
  2. Add the Glitchy offer Copy the affiliate link from Glitchy's Offers section. In ClickFlare, create a new offer, choose Glitchy as the network, paste the link and toggle Append Click ID.
  3. Set the postback in Glitchy Open the same offer in Glitchy, paste the ClickFlare postback into Conversion Attribution Postback and click Add Postback URL. A preview shows under the field.
  4. Create the campaign Select your Glitchy offer and a traffic source in a new ClickFlare campaign, then use the campaign URL in your ads.
Postback URL to paste in each Glitchy offer
https://webeasyhit.com/cf/cv?click_id={source}&payout={payout}
app.clickflare.com/integrations
GL
Glitchy
Affiliate network
Connected
Glitchy account connected
Signed in from ClickFlare
Cost syncing
Spend matched to campaigns
Conversions sent back
Your chosen events
Glitchy template selected
Macros pre-filled
Tracking URL in Glitchy
Click ID captured
Conversions reported
Payout included where supported
Glitchy connected
Credentials saved in ClickFlare
Conversion event set
Click ID passed to the feed
Revenue syncing
On the feed's schedule
Glitchy added
Offer URL carries the click ID
Postback set in Glitchy
Payout and event included
Conversions arriving
Matched to the click
Glitchy connected
Click ID kept to checkout
Events mapped
View, cart, checkout, purchase
Purchases tracked
Order value in reports
Ready to track
Without the postback in Glitchy, clicks still show in ClickFlare but conversions don't. Test a click and a conversion before you scale.
Glitchy setup guide
Open the guide
In your reports

What you see once it's connected

  • Conversions per offer
  • Payout per campaign
  • EPC by traffic source
  • ROI by lander
  • Offer comparison by source
Use cases

How media buyers run it

Offer testing

Add several Glitchy offers to a campaign and compare them on payout from the same traffic. Keep the offer that pays best.

Push → Glitchy offer

Send push or pop traffic straight to a Glitchy offer and judge each source on the payout Glitchy reports, not on clicks.

Native → lander → offer

Put a presell page in front of a Glitchy offer and see which lander turns clicks into paid conversions.
Frequently asked questions

Questions about Glitchy

No items found.
Setup guides
Glitchy setup guide
{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with Glitchy?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. ClickFlare has a ready-made Glitchy template that generates the postback URL. Glitchy sends conversions back by S2S postback."}}, {"@type": "Question", "name": "Which parameter carries the ClickFlare click ID to Glitchy?", "acceptedAnswer": {"@type": "Answer", "text": "source. Toggle Append Click ID on the offer and ClickFlare adds source={cf_click_id}. Glitchy returns the value in its {source} macro."}}, {"@type": "Question", "name": "Where do I add the postback in Glitchy?", "acceptedAnswer": {"@type": "Answer", "text": "At the offer level. Open the offer, paste the ClickFlare postback into Conversion Attribution Postback and click Add Postback URL."}}, {"@type": "Question", "name": "Can I track Glitchy payouts in ClickFlare?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Keep the {payout} token in the postback and ClickFlare logs revenue for each conversion."}}, {"@type": "Question", "name": "Do I repeat the setup for every Glitchy offer?", "acceptedAnswer": {"@type": "Answer", "text": "You add the Glitchy network once. Each new offer is added under Offers, linked to that network, and gets its own postback in Glitchy."}}, {"@type": "Question", "name": "What happens if I skip the Glitchy postback?", "acceptedAnswer": {"@type": "Answer", "text": "Clicks are still tracked in ClickFlare, but conversions are not recorded. The postback is required for conversion attribution."}}]}