Advertiser tracking guide

Advertiser postback setup for CPA and CPI campaigns

Use CPAlead postbacks to send approved installs, leads, or actions back to CPAlead after your tracker receives a conversion. The key is to store the CPAlead click ID from the tracking URL and return that same value as click_id.

Start Advertiser Signup View Pricing

Postback URL format

Your account has a unique postback ID. Use it with the CPAlead click ID that your tracking system saved from the original click.

Example

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

Multiple rewarded events

Keep the original click_id. For each completed event, send its numeric event_id or its exact saved event_name. Include campaign_id for extra protection. Each reward uses the payment saved in your campaign.

Send the Event ID number or the exact event name shown in your campaign. If your tracker sends a different name or code, save it as an extra tracker value.

Set a separate payment for each event. Each event can be paid once per participant. Include the install as an event if you want to pay for it.
Participants have 30 days from their click to complete events. Keep enough balance for later events, including while the campaign is paused. Event details and payments cannot change after the first click.
The daily limit counts each participant at their first paid event. Later events do not count again. Reaching the limit stops new traffic. Earlier clicks can still earn rewards within 30 days, so pending completions may exceed the limit.
Multiple events use standard server postbacks, or AppsFlyer for CPI campaigns. Tracking pixels are not supported.
Multiple-event campaigns can run on Offerwall V2, the offers API, and direct links. Classic offerwalls and lockers are not supported yet.
Each event can arrive in any order. Retrying the same click_id and event_id returns postback_duplicate without another charge. If the response says low_balance, add funds and retry the same event after the Retry-After delay.
A hold of up to $3.00 may apply when your postback has a missing or invalid click ID, mismatched campaign information, or a missing or invalid event ID on a verified event campaign click. Use the original CPAlead click ID and, for event campaigns, the saved event ID to resolve the issue.

Event postback example

Example: for Event ID 1 named 150gems, send event_id=1 or event_name=150gems. event_id=150gems also works. Use the same original click_id for every reward.

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

Replace SAVED_EVENT_ID with the event number. To send a name instead, use event_name with the exact saved event name or tracker value.

AppsFlyer event rewards

For AppsFlyer CPI events, map each saved numeric event ID as the AppsFlyer partner event identifier. The optional appsflyer_event_name must match the SDK name exactly, including capital letters. Different rewards may use the same SDK name when the partner event identifiers distinguish them. Name-only callbacks require a unique saved name. To pay for installs, set one reward name mapping to install and use an explicit event_type=install callback; a blank event name does not mean install.

Enable CPAlead-attributed in-app event postbacks in the AppsFlyer integration and review the dedicated callback templates in Postback Setup. Do not add the standard /aff_lsr advertiser URL to AppsFlyer. In-app callbacks send event_type=in_app, partner_event_id, event_name, app_id, and the original clickid. Review any custom sender IP whitelist. Ask CPAlead support to check whether AppsFlyer has enabled optional retries for 5xx responses; it can retry four times at 15-minute intervals after the first attempt. Tracking cost macros stay zero for event campaigns; event reports show actual credited reward spend. Saving a CPAlead campaign does not change the AppsFlyer account.

Setup steps

The flow works when the CPAlead click ID is preserved.

CPAlead credits publishers by matching the conversion postback to the click that sent the user to your campaign.

Add CPAlead tracking to your campaign URL

Place the CPAlead click ID macro into your tracker so every visitor can be matched later.

Store the CPAlead click ID

Save our click ID in your tracking platform when the user lands on your offer or redirect path.

Send the conversion back

When the install, lead, or action is approved, call the CPAlead postback URL with the same click_id.

Include campaign_id when possible

Campaign ID is recommended because it helps CPAlead match reporting and troubleshoot faster.

Required values

Parameters CPAlead needs on your conversion postback.

id Required

Your CPAlead advertiser postback ID. You can find it in the advertiser dashboard after you create an account.

click_id Required

The exact CPAlead click ID you received when the user clicked your campaign tracking URL.

campaign_id Recommended

The CPAlead campaign ID. Include it when possible to improve matching and support review.

event_id / event_name Required for events

AppsFlyer CPI installs

Mobile app owners and agencies can use AppsFlyer attribution.

CPAlead supports AppsFlyer setup for CPI campaigns when you own the app or have access to the app attribution account. Use the full AppsFlyer tracking link and keep CPAlead's click ID in the clickid parameter.

AppsFlyer link example

https://app.appsflyer.com/[YOUR_APP_ID]?pid=cpalead_int&af_click_lookback=5d&clickid={CLICK_ID}&af_siteid={PUBLISHER_ID}&af_cost_value={PAYOUT}&af_cost_currency=USD&af_cost_model=CPI

Use a full https://app.appsflyer.com/[APP_ID] tracking link.
Keep pid=cpalead_int for normal CPAlead AppsFlyer setup.
Use clickid={CLICK_ID} so AppsFlyer saves the CPAlead click ID.
Include af_siteid={PUBLISHER_ID} and the cost parameters required by the campaign form.
Do not use af_prt for normal CPAlead setup.

Example URLs

Store our click ID, then send it back at conversion time.

Example tracking URL

https://your-tracker.example/click?cpalead_click_id={CLICK_ID}&campaign_id={CAMPAIGN_ID}

Replace the placeholder macros with the values your tracker uses to save CPAlead click ID and campaign ID.

Example CPAlead postback URL

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

Send this URL only when your tracker confirms a real conversion.

Common setup mistakes

Avoid the issues that make advertiser postbacks fail.

Sending your own tracker click ID instead of the CPAlead click ID.
Leaving a placeholder macro in the final postback URL.
Sending conversions without campaign_id when your tracker can provide it.
Testing with fake click IDs instead of using the guided test in the advertiser dashboard.

Get help from your AI chatbot

Copy this prompt when you want tracker-specific setup help.

Paste this into ChatGPT, Claude, Gemini, or another AI assistant. It asks for the tracking system, network, tracking URL, and AppsFlyer details before suggesting setup steps.

You are helping me set up advertiser tracking for a CPAlead campaign.

CPAlead tracking facts:
- CPAlead needs the advertiser postback to include id, click_id, and campaign_id when available.
- id is my CPAlead advertiser postback ID.
- click_id must be the exact CPAlead click ID that was saved from the original tracking URL.
- campaign_id is the CPAlead campaign ID and should be included when my tracker or network can send it.
- Standard CPAlead postback example:
  https://net.go2trck.org/aff_lsr?id=YOUR_POSTBACK_ID&click_id={CLICK_ID}&campaign_id={CAMPAIGN_ID}
- Do not invent a saved click parameter. If you cannot tell where CPAlead's click ID is stored, ask me for the exact tracking URL or tell me to confirm the macro with my tracker or network.

AppsFlyer CPI setup facts:
- CPAlead supports AppsFlyer setup for CPI mobile app campaigns.
- The tracking link should use the full https://app.appsflyer.com/[APP_ID] URL.
- Normal CPAlead AppsFlyer setup should keep pid=cpalead_int.
- CPAlead's click ID should usually be saved as clickid={CLICK_ID}.
- The link should include af_siteid={PUBLISHER_ID}.
- The campaign form may require cost parameters such as af_cost_value, af_cost_currency, and af_cost_model.
- Do not use af_prt for normal CPAlead setup.

Please ask me these questions before giving final setup instructions:
1. Am I using AppsFlyer, Voluum, Everflow, HasOffers/TUNE, CAKE, a custom tracker, a mobile measurement partner, or an affiliate network?
2. Is my CPAlead campaign CPA, CPI install, or CPI in-app event?
3. What is the exact tracking URL I plan to submit to CPAlead?
4. Which parameter in that tracking URL stores CPAlead's {CLICK_ID}?
5. What macro does my tracker or network use to send the saved CPAlead click ID back in a postback?
6. Do I have my CPAlead advertiser postback ID and CPAlead campaign ID?

After I answer, give me:
- The corrected tracking URL I should submit to CPAlead.
- The postback URL I should add to my tracker, network, or AppsFlyer setup.
- Any missing macros or risky parameters.
- A short checklist I can verify before launching traffic.

Multiple rewarded event campaigns:
- First confirm whether I selected one conversion or multiple rewarded events. CPA and CPI support both; CPC does not support events.
- For multiple events using a standard tracker, use server postbacks with id, the original real click_id, and either its numeric event_id or its exact saved event_name. Text values in event_id also match saved names or postback_event_value. Send numeric external codes through event_name. All supplied identifiers must identify the same reward. Include campaign_id for extra protection; CPAlead includes it in generated campaign postback URLs and checks it when supplied. Never invent event IDs or click IDs, and never send a payout to override the agreed reward.
- Each event pays once within 30 days of the original click, in any order. Include the install in the event list only when I want to pay for it. Repeating the same click_id and event_id safely returns postback_duplicate without another payment.
- Keep enough funds for pending events, including after pausing traffic. For low_balance, add funds and retry the same event after Retry-After. The daily cap counts each participant at their first paid event and stops new traffic; pending clicks remain eligible within the completion window.
- The optional postback_event_value field adds an exact tracker name or code. Check event_rules for availability. It can be corrected after traffic with an audit trail; reward IDs, names and prices stay locked.
- Mode and event definitions cannot change after traffic starts. Copy the campaign to change them. Multiple events support standard postbacks or AppsFlyer for CPI; tracking pixels, classic offerwalls and lockers are unsupported. Tracking method and AppsFlyer mapping also freeze after real traffic.
- Offerwall V2 shows event offers only with a stable explicit publisher subid. Use the same user ID on every visit; an advertising ID alone is not enough for V2. Returning participants use the original click and 30-day deadline; another visit does not restart rewards. For direct links, a first-party browser cookie supports returning visitors without an explicit ID, but it cannot preserve identity after cookies are cleared or the browser or tracking domain changes. Recommend stable publisher user IDs in subid.
- AppsFlyer single-goal CPI uses CPAlead Integrated Partners. Do not suggest adding the standard /aff_lsr URL to AppsFlyer. For one in-app event, its AppsFlyer name must match the single campaign conversion goal.
- Explain that temporary AI campaign drafts cannot configure or test tracking. Use the signed-in Guided Test with real campaign and event IDs.
- For AppsFlyer CPI events, map each saved numeric event ID as the AppsFlyer partner event identifier. The optional appsflyer_event_name must match the SDK name exactly, including capital letters. Different rewards may use the same SDK name when the partner event identifiers distinguish them. Name-only callbacks require a unique saved name. To pay for installs, set one reward name mapping to install and use an explicit event_type=install callback; a blank event name does not mean install.
- Enable CPAlead-attributed in-app event postbacks in the AppsFlyer integration and review the dedicated callback templates in Postback Setup. Do not add the standard /aff_lsr advertiser URL to AppsFlyer. In-app callbacks send event_type=in_app, partner_event_id, event_name, app_id, and the original clickid. Review any custom sender IP whitelist. Ask CPAlead support to check whether AppsFlyer has enabled optional retries for 5xx responses; it can retry four times at 15-minute intervals after the first attempt. Tracking cost macros stay zero for event campaigns; event reports show actual credited reward spend. Saving a CPAlead campaign does not change the AppsFlyer account.

Ready to connect advertiser tracking?

Create an advertiser account, add your campaign, and use postback tracking before you scale traffic.

Start Advertiser Signup Advertiser Pricing