The Complete Beginner's Guide to Postback Tracking for CPAlead Advertisers

The number 1234567890 below is an illustration only. Actual CPAlead click IDs contain digits; always return the exact value CPAlead put in your tracking URL. Never send the example number as a live test.

Adding a CPI or CPA offer to CPAlead is easy once you can understand how postback tracking works. We're writing this as a follow-up guide to CPAlead Advertiser Guide: Setting Up Your First Campaign . Let's learn about postback tracking in the simplest way possible! Imagine you're running a lemonade stand (your offer), and CPAlead is your friendly neighbor helping to send customers to you. Here's how it works:

1. When CPAlead sends a customer (traffic) to your lemonade stand, they give the customer a special numbered ticket (for example, ticket #1234567890)
2. The customer takes this numbered ticket to your stand (just like a user following your tracking URL with the click_id parameter)
3. When the customer buys lemonade (converts), your stand keeper (your network) takes the ticket and reads the number
4. Your stand keeper then sends a message to CPAlead saying "Ticket #1234567890 made a purchase!" (this is what happens when the postback URL is triggered)
5. CPAlead matches this ticket number to their records and knows exactly which customer made the purchase

This way, CPAlead knows exactly which customers bought lemonade and can reward the neighbor who sent them! We'll show you exactly how to set this up with real examples.

What is a Click ID?

A click ID is like a special sticker we put on each click. When someone clicks your offer:

• CPAlead generates a unique identifier in the following format: 1234567890. We will use this as an example.
• This identifier follows the user, similar to a name tag.
• When the user installs your app or completes an action, your network sends this identifier back to CPAlead by inserting it into the CPAlead postback URL as the click ID (e.g., 1234567890) and then programmatically triggering the CPAlead postback URL that willl look like this:
  https://net.go2trck.org/aff_lsr?id=YOUR_POSTBACK_ID&click_id=1234567890.
• When CPAlead receives a postback containing the identifier (e.g., 1234567890), it recognizes that a lead has been generated from the corresponding click. Using this identifier, CPAlead retrieves all relevant details, such as your advertiser ID, campaign ID, and the sub-ID of the user who clicked. CPAlead then processes the reward accordingly.

How to Find Your Network's Click ID Parameter

Not sure what parameter your network uses? Here's what to do:

1. Open your network's support center or documentation
2. Search for "click ID parameter" or "tracking parameter"
3. Or simply ask your network manager: "What parameter do you use to store click IDs?"

Example Setups Made Simple

http://yournetwork.com/click?offer=123&aff_sub={CLICK_ID}

https://net.go2trck.org/aff_lsr?id=YOUR_POSTBACK_ID&click_id={aff_sub}

http://network.example.com/track?campaign=456&sid={CLICK_ID}

https://net.go2trck.org/aff_lsr?id=YOUR_POSTBACK_ID&click_id={sid}

http://tracker.net/path?offer=789&click={CLICK_ID}

https://net.go2trck.org/aff_lsr?id=YOUR_POSTBACK_ID&click_id={click}

http://track.domain.com/click?id=101112&sub1={CLICK_ID}

https://net.go2trck.org/aff_lsr?id=YOUR_POSTBACK_ID&click_id={sub1}

http://affnetwork.com/track?offer=131415&clickid={CLICK_ID}

https://net.go2trck.org/aff_lsr?id=YOUR_POSTBACK_ID&click_id={clickid}

Real-World Click ID Examples

Let's see how our example click ID (1234567890) would look in actual tracking and postback URLs:

http://yournetwork.com/click?offer=123&aff_sub={CLICK_ID}

http://yournetwork.com/click?offer=123&aff_sub=1234567890

https://net.go2trck.org/aff_lsr?id=YOUR_POSTBACK_ID&click_id={aff_sub}

https://net.go2trck.org/aff_lsr?id=YOUR_POSTBACK_ID&click_id=1234567890

Postbacks for multiple event rewards

A CPA or CPI campaign can pay for several events on the same original click. The tracker must tell CPAlead which saved event was completed.

For standard postbacks, send your own postback ID, the original saved click_id, and a value that identifies the completed reward. Include campaign_id for extra protection; it must match the original click's campaign. Use the account-generated URL and never invent IDs.

https://net.go2trck.org/aff_lsr?id=YOUR_POSTBACK_ID&campaign_id=YOUR_CAMPAIGN_ID&click_id=REAL_CLICK_ID&event_id=1

• Event 1: An install pays $0.50. Send event_id=1 only if 1 is the saved ID for that install reward.
• Event 2: Reaching level 5 pays $1.25. Send the same original click_id with event_id=2 if 2 is the saved ID for that reward.
• Sending event 1 again does not pay it twice. Another eligible event on the same click can still pay. Each accepted event has its own lead_id.

Missing or incorrect event values return HTTP 400 without paying the reward. Correct the mapping, then resend the same real click with the matching event number, name or tracker value supported by your setup. Do not guess an install event or substitute another click. Existing holds still need review on the Postback Holds page.

Report each event within 30 days of the original click. If the response is HTTP 503 low_balance, add funds and retry the identical event after the Retry-After delay while it is still within that window. A reward must be funded in full.

For CPI with AppsFlyer, use CPAlead's Integrated Partner setup and map the saved numeric reward IDs to partner event identifiers. Installs need an explicit install reward. Do not paste the standard /aff_lsr URL into AppsFlyer.

See the event postback instructions for setup and response details.

Test before sending traffic

• Open your signed-in Postback page and use Guided Test for the campaign.
• Open the temporary tracking link and follow the test instructions. For an event campaign, send the saved event ID for the action you are testing.
• Check the test result and postback logs. A successful guided test records receipt without creating a paid conversion.
• If a test fails, fix the stored click parameter or event mapping and try again within the test window. Never make up a click ID.

Use the same parameter to store and return CPAlead's click ID, and keep working examples for future campaigns.

Need help?

• Ask your tracker which parameter safely stores CPAlead's click ID and which callback field can return your saved event ID.
• You can ask an AI chat to explain the tracking documentation. Remove private postback IDs, tokens, and real visitor details before sharing examples.
• Contact CPAlead support if a real click or event still cannot be matched after checking the setup.

Noticed an error or an aspect of this post that requires correction? Please provide the post link and reach out to us. We appreciate your feedback and will address the issue promptly.