Pracharak tracking guide

Pracharak postback setup for CPA and CPI campaigns

CPAlead postbacks ka use karke approved installs, leads, ya actions ko conversion milne ke baad wapas CPAlead par bejo. Mukhya baat yeh hai ki tracking URL se CPAlead click ID ko store karo aur usi value ko click_id ke roop mein return karo.

Pracharak Signup Shuru Karo Moolya Dekho

Postback URL format

Aapke account ka ek anokha postback ID hai. Ise CPAlead click ID ke saath use karo jo aapke tracking system ne original click se save kiya tha.

Udaharan

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

कई इनाम वाले इवेंट

Original click_id wahi rakhein. Har poore hue event ke liye numeric event_id ya bilkul sahi save kiya gaya event_name bhejein. Zyada suraksha ke liye campaign_id shamil karein. Har reward ki payment campaign mein save ki gayi rakam hogi.

Campaign mein dikhaya gaya Event ID number ya event ka bilkul sahi naam bhejein. Agar tracker alag naam ya code bhejta hai, use extra tracker value ke roop mein save karein.

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.
इवेंट किसी भी क्रम में आ सकते हैं। वही click_id और event_id दोबारा भेजने पर बिना दोबारा शुल्क के postback_duplicate मिलता है। low_balance मिलने पर धन जोड़ें और Retry-After की अवधि के बाद वही इवेंट फिर भेजें।
Agar postback mein click ID missing ya invalid ho, campaign ki jaankari match na kare, ya verified event campaign click par event ID missing ya invalid ho, to $3.00 tak ka hold lag sakta hai. Issue resolve karne ke liye original CPAlead click ID aur event campaigns ke liye saved event ID use karein.

इवेंट पोस्टबैक का उदाहरण

Udaharan: Event ID 1 ka naam 150gems hai to event_id=1 ya event_name=150gems bhejein. event_id=150gems bhi chalega. Har reward ke liye wahi original click_id use karein.

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

SAVED_EVENT_ID ki jagah event ka number dalein. Naam bhejne ke liye event_name mein save kiya gaya sahi naam ya tracker value dalein.

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.

Sthapna ke charan

Jab CPAlead click ID surakshit rakha jata hai, tab pravah sahi kaam karta hai.

CPAlead publisheron ko conversion postback ko us click se milakar credit deta hai jo user ko aapke campaign tak le gaya tha.

Aapke campaign URL mein CPAlead tracking jodo

CPAlead click ID macro ko apne tracker mein rakho taaki har visitor baad mein match ho sake.

CPAlead click ID store karo

Jab user aapke offer ya redirect path par land kare, tab hamara click ID apne tracking platform mein save karo.

Conversion wapas bejo

Jab install, lead, ya action approve ho jaye, tab same click_id ke saath CPAlead postback URL ko call karo.

Jab mumkin ho campaign_id shamil karo

Campaign ID ki sifarish ki jati hai kyonki ye CPAlead ko reporting match karne aur jaldi troubleshoot karne mein madad deta hai.

Aavashyak values

Parameters jo CPAlead ko aapke conversion postback mein chahiye.

id Aavashyak

Aapka CPAlead advertiser postback ID. Account banaane ke baad use advertiser dashboard mein dhoondh sakte ho.

click_id Aavashyak

Vahi exact CPAlead click ID jo aapne tab paaya tha jab user ne aapke campaign tracking URL par click kiya tha.

campaign_id Sujhaav wala

CPAlead campaign ID. Jab mumkin ho tab ise shamil karo taaki matching aur support review behtar ho.

event_id / event_name इवेंट के लिए आवश्यक

AppsFlyer CPI installs

Mobile app owners aur agencies AppsFlyer attribution ka use kar sakte hain.

Jab aapke paas app ka maalikaan ho ya app attribution account ki pahunch ho, tab CPAlead CPI campaigns ke liye AppsFlyer setup ko support karta hai. Pura AppsFlyer tracking link use karo aur CPAlead's click ID ko clickid parameter mein rakho.

AppsFlyer link udaharan

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

Pura https://app.appsflyer.com/[APP_ID] tracking link use karo.
Normal CPAlead AppsFlyer setup ke liye pid=cpalead_int rakho.
AppsFlyer CPAlead click ID ko save kare isliye clickid={CLICK_ID} use karo.
af_siteid={PUBLISHER_ID} aur campaign form ke mutabik zaroori cost parameters shamil karo.
Normal CPAlead setup mein af_prt ka use mat karo.

Udaharan URLs

Hamara click ID store karo, phir conversion samay use wapas bejo.

Udaharan tracking URL

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

Placeholder macros ko un values se badlo jo aapka tracker CPAlead click ID aur campaign ID save karne ke liye use karta hai.

Udaharan CPAlead postback URL

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

Yeh URL sirf tab bejo jab aapka tracker ek sahi conversion ki pushti kar de.

Aam setup galtiyan

Un maslon se bacho jo advertiser postbacks ko fail karte hain.

Apne tracker ka click ID bejne ke badle CPAlead click ID ko na bhejna.
Final postback URL mein placeholder macro chhod dena.
Jab aapka tracker campaign_id de sakta ho tab uske bina conversions bejna.
Guided test ko advertiser dashboard mein use karne ki bajaye fake click IDs se test karna.

Apne AI chatbot se madad lo

Jab aap tracker-vishesh setup madad chahte ho toh ye prompt copy karo.

Ise ChatGPT, Claude, Gemini, ya kisi aur AI assistant mein paste karo. Yeh setup steps sujhaane se pahale tracking system, network, tracking URL, aur AppsFlyer details maangta hai.

Aap meri madad kar rahe ho CPAlead campaign ke liye advertiser tracking setup karne mein.

CPAlead tracking facts:
- CPAlead ko advertiser postback mein id, click_id, aur campaign_id, jab available ho, shamil chahiye.
- id mera CPAlead advertiser postback ID hai.
- click_id bilkul vahi CPAlead click ID hona chahiye jo mool tracking URL se save hua tha.
- campaign_id CPAlead campaign ID hai aur use tab shamil karna chahiye jab mera tracker ya network use bhej sake.
- Standard CPAlead postback udaharan:
  https://net.go2trck.org/aff_lsr?id=YOUR_POSTBACK_ID&click_id={CLICK_ID}&campaign_id={CAMPAIGN_ID}
- Kisi saved click parameter ki kalpana mat karo. Agar aap yeh nahin batā sakte ki CPAlead ka click ID kahaan store hai, toh mujhse exact tracking URL maango ya mujhe kaho ki apne tracker ya network ke saath macro confirm karun.

AppsFlyer CPI setup facts:
- CPAlead CPI mobile app campaigns ke liye AppsFlyer setup ko support karta hai.
- Tracking link mein full https://app.appsflyer.com/[APP_ID] URL hona chahiye.
- Normal CPAlead AppsFlyer setup mein pid=cpalead_int rakha jana chahiye.
- CPAlead click ID aam tor par clickid={CLICK_ID} ke roop mein save hona chahiye.
- Link mein af_siteid={PUBLISHER_ID} shamil hona chahiye.
- Campaign form mein af_cost_value, af_cost_currency, aur af_cost_model jaisi cost parameters ki zaroorat ho sakti hai.
- Normal CPAlead setup ke liye af_prt ka use mat karo.

Mehraani karke final setup instructions dene se pahale mujhse ye prashn pucho:
1. Kya main AppsFlyer, Voluum, Everflow, HasOffers/TUNE, CAKE, custom tracker, mobile measurement partner, ya affiliate network use kar raha hoon?
2. Kya mera CPAlead campaign CPA, CPI install, ya CPI in-app event hai?
3. Exact tracking URL kya hai jo main CPAlead ko submit karne wala hoon?
4. Us tracking URL mein kaunsa parameter CPAlead ke {CLICK_ID} ko store karta hai?
5. Mera tracker ya network saved CPAlead click ID ko postback mein wapas bejne ke liye kaunsa macro use karta hai?
6. Kya mere paas CPAlead advertiser postback ID aur CPAlead campaign ID hai?

Jab main jawab doon, mujhe ye do:
- Sahi kiya gaya tracking URL jo mujhe CPAlead ko submit karna chahiye.
- Postback URL jo mujhe apne tracker, network, ya AppsFlyer setup mein jodna chahiye.
- Koi missing macros ya risk wala parameters.
- Ek chhoti checklist jo traffic launch karne se pahale main verify kar saku.

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.

Kya aap advertiser tracking ko jodne ke liye tayar ho?

Advertiser account banao, apna campaign jodo, aur traffic scale karne se pahale postback tracking ka use karo.

Pracharak Signup Shuru Karo Pracharak Moolya