Affiliate lead form tracking: connect the form to approved leads

Affiliate lead form tracking works only when the system that receives the form keeps the same click ID until it reports the lead back. A hosted page can explain the offer and send a visitor through a tracked click. The advertiser's form or CRM must save that identifier with the submission, qualification decision, and approved outcome.

Tracked attributes callbacks to recorded clicks. It does not qualify leads, replace your CRM, or infer a later approval from a button click.

Map the lead path before building the page

Write down the owner of each handoff:

Ad → Tracked campaign page → /click/1 → advertiser form
   → lead record with Tracked click ID → qualification or approval
   → advertiser postback → Tracked journey and report

The form may live on the advertiser's site, an affiliate network's page, or another system you control. In each case, identify the field it accepts for a sub-ID or click reference. Do not assume that sub1 or any other parameter name is universal.

If you embed a form directly on your hosted page, its submission still needs an explicit way to carry and store the correct Tracked identifier. Simply placing an HTML form on a tracked page does not automatically turn its submission or a later CRM update into an attributed conversion.

Pass the offer-click ID to the form system

For an advertiser-hosted form, put the form URL in the Tracked offer configuration and insert Tracked's offer-click macro into the advertiser's supported field. An illustrative offer URL is:

https://advertiser.example/apply?sub1={{click.id}}

Then send the landing page button to the campaign-relative tracked click path:

<a href="/click/1">Check eligibility</a>

The outbound click should replace {{click.id}} with a real Tracked offer-click ID. The advertiser should store that value on the lead record. Inspect the final request or the advertiser's test record to verify the handoff. A literal {{click.id}}, an empty field, or the page's impression ID will not identify the intended offer click later.

Keep personal form data in the advertiser or CRM system that owns it. The callback needs the click reference and event details, not a copy of the applicant's entire form submission.

Decide which lead stage is the paid conversion

One form submission can lead to several business decisions. Name them before wiring callbacks:

Stage	Example owner	Tracking question
Submitted lead	Form system	Did a valid submission reach the system?
Qualified lead	CRM or sales team	Did it meet the agreed criteria?
Approved lead	Advertiser or network	Is it accepted for payout?

For the current Tracked callback contract, an untyped postback can record the primary conversion and its payout. A callback with conversion_type or type records a secondary event with zero payout. If approval is the paid event, configure it as the primary outcome; use typed events for earlier stages you want to inspect. The lead-generation conversion guide covers stage definitions and event mapping in more detail.

Do not send the same paid approval once as a form submission and again as an approval. That would make a campaign appear to have two paid conversions when it has one.

Return the stored ID in the advertiser postback

After the advertiser confirms an event, its server sends a callback to the Tracked domain serving the campaign. The parameter on Tracked's side is click_id, even when the advertiser stored the value under another name:

https://YOUR_TRACKED_DOMAIN/postback?click_id=TRACKED_CLICK_ID&conversion_id=LEAD_EVENT_ID&payout=25

This is an example, not a URL to paste with placeholder values. Use the advertiser's documented callback macros. A stable conversion_id helps identify retries of the same business event. Use a distinct event identity for a later, genuinely separate stage.

Test with one identifiable lead. Confirm the advertiser received the click ID, stored it with the form record, and returned it in the callback. Then find the resulting event under the correct page, offer, campaign, and click in Tracked. A 200 callback response alone does not prove the event was stored or that the advertiser approved the lead. The postback guide explains the response and verification checks.

Diagnose the first missing handoff

• Form visit exists, but no Tracked offer click: check the landing page button's /click/N target.
• Tracked click exists, but advertiser has no ID: check the offer URL macro and the advertiser's accepted field.
• Advertiser has the ID, but Tracked has no lead: inspect the callback delivery, click_id, event mapping, and matched journey.
• Raw leads appear, but approvals do not: ask whether the advertiser actually sends an approval event and whether it uses the stored ID.
• Payout is missing: check whether the paid event was sent as an untyped primary callback; explicitly typed events currently record zero payout.

The useful distinction is operational: a page can generate form visits while the callback path is broken. Repair the handoff before changing ad spend or page copy.

Tracked puts the hosted page, campaign route, offer click, callback, and attributed report in one workspace. Start free and connect a lead-form campaign.

Frequently asked questions

Does Tracked automatically track every form submission on a hosted page?

No. The form system must send an event that Tracked can match to a recorded click. An HTML form on a page is not, by itself, an attributed conversion.

Which ID should the advertiser save with a lead?

Save the Tracked offer-click ID passed by the outgoing offer URL. The advertiser can call its storage field sub1 or another supported name, but it must return the same value as click_id in the postback.

Can I track submitted and approved leads separately?

Yes. Define the stages and map distinct events. In the current callback path, the untyped primary event can carry payout; explicitly typed secondary events record zero payout.

Does a successful postback prove the lead was approved?

No. Approval is the advertiser's business decision. A successful request is only one part of the delivery path; confirm the event type and matched report record.