
An approved Sweeply sale is recorded in the Sweeply dashboard, not in Google Ads. Without a postback connecting the two, the campaign reports zero conversions and automated bidding optimizes blind. The fix is to keep the click's GCLID and set up one global postback per account.
The campaign that sells but looks like it doesn't
Looking only at Google Ads, you would pause the ad that is selling. Sweeply shows an approved commission; Google Ads shows an expensive campaign with no results.
It is not only a reporting problem. Maximize conversions and target CPA rely on recorded conversions to learn who buys. Without them, the algorithm learns from clicks.
A postback is a notice an affiliate network sends to another system when a conversion changes status. Sweeply runs on Scaleo and includes, in that notice, the sub IDs that came with the click.
What Sweeply is
Sweeply is a CPA network with straight-sale nutra and e-commerce offers. The affiliate picks an offer, promotes it with their own link and gets paid per approved sale.
How do you track Sweeply sales in Google Ads?
Three pieces: GCLID in the link, a global postback in Sweeply and the conversion imported into Google Ads.
- 1Keep the click's GCLID and pass it in the affiliate link, in a sub ID (for example, sub_id2).
- 2In the Sweeply dashboard, open Tools → Global Postbacks → Add Global Postback.
- 3Fill in Triggered for = Approved, Goal Type = All, Method = Postback (Recommended) and paste your tracker's URL, with the macro for the sub ID that carries the GCLID.
- 4In your tracker, send the sale to Google Ads as an offline conversion tied to the GCLID.
Keep Triggered for on Approved, never All. With All, Sweeply also reports conversions that may still be rejected, and the campaign learns from sales that may never become commission.
Why the GCLID has to go in a sub ID
It is what ties the sale to the exact ad. The postback hands the click's sub IDs to your tracker; without the GCLID among them, the sale arrives with no campaign attached.
Building that parameter by hand in every link is where most affiliates slip: one wrong sub ID and the sale is orphaned. That is why it pays to automate the path from click to link.
One global postback covers every offer you promote on Sweeply. Four fields, set once per account.
Read alsoHow to Track Affiliate Sales on Google AdsFrequently asked questions
Do I need one postback per Sweeply offer?
No. The global postback covers every offer in your account. Only create a per-offer postback if you want to separate one on purpose.
Does the sale show up right away?
It shows up when Sweeply approves the conversion, because the postback fires only on Approved. Pending sales arrive after approval.
The sale didn't show up. What should I check?
Check that the postback is under Global Postbacks with Triggered for on Approved, that the pasted URL has no trailing space and that the GCLID goes in the same sub ID the postback reads.
Approved sales Google Ads can see
The gap between a campaign that seems not to sell and one that learns is a postback set up once. With every sale tied to its ad, budget goes to what actually sells.
If you want to see every Sweeply sale in Google Ads
AdsX has over 5,000 users and ties every Sweeply sale to the ad that brought it, with no code.
More on Affiliate tracking
How to Track Which Google Ads Account Made Each Sale