Lead generation conversion tracking: raw leads, qualified leads, and customers

Lead generation conversion tracking connects the ad click to a lead, a later quality decision, and the customer or approved event that matters to the business. Tracked keeps the original click context attached to callbacks so you can inspect those stages in reports and journeys. It does not decide whether a lead is valid, qualified, or ready to buy.

A cheap form submit can look good while the advertiser rejects it. An approved event can be more useful, but it depends on the advertiser or network returning the original identifier.

Define the lead stages before you send events

Use names that describe the business decision, not whatever label a network happens to use. A practical funnel looks like this:

Stage	Meaning	Who owns the decision?
Lead	A form submission, call, signup, or other agreed first action	Your form, advertiser, or lead source
Qualified lead	A lead that meets the agreed audience, need, market, or sales criteria	The advertiser, sales team, CRM, or network
Approved lead	A lead accepted under the payout or compliance contract	The advertiser or affiliate network
Customer / converted lead	A sale, closed deal, funded account, or other final event	The business or offer owner

These labels are not interchangeable. “Approved” can mean a network accepted a lead for payout; “customer” usually means a deeper commercial outcome. Keep them separate when timing, payout, or action differs. Google Ads makes the same distinction in its current documentation: qualified and converted leads are different stages, and separate conversion actions provide clearer reporting. Use the traffic platform’s definitions instead of treating its labels as universal.

Keep the click ID through the handoff

The useful path is:

Ad click → Tracked campaign → form or offer → lead event
  → advertiser or CRM decision → postback with click ID → Tracked report and journey

The click ID is the join key. Pass the Tracked offer-click ID into the form or offer system using its supported field, and keep it with the lead record until the next stage is known. Do not substitute a page impression ID or the ad platform’s click ID. The affiliate campaign tracking setup covers this handoff.

For an advertiser-hosted form, the affiliate lead-form tracking walkthrough shows the page button, offer URL macro, saved form field, and returning callback as one testable path.

Tracked’s public postback accepts an explicit event type or the campaign’s configured default. Its event mapping lets an advertiser name such as qualified resolve to a stable Tracked category when configured. Parameter names and delivery options still belong to the provider. A successful HTTP response proves transport; check the matched click, event type, payout, and report row separately.

Decide which stage is the primary paid outcome. In the current callback handler, an untyped callback records the primary conversion and can carry payout; a callback with conversion_type or type records a secondary event with zero payout. For example, a paid approved lead can be the untyped primary event, while an earlier qualification signal uses a mapped secondary type. Do not send every stage as a primary conversion or expect a typed event to add revenue. The postback setup examples show both request shapes.

Choose a reporting stage and an optimization stage

Report each available stage, then decide which stage should guide a buying decision:

• Use the raw lead as an early signal when qualification is delayed or sparse.
• Use qualified or approved leads when the advertiser can return them reliably and the stage has a clear definition.
• Use customer or converted events when the sale is the actual economic outcome and the delay is acceptable for the traffic source.

Do not silently replace one stage with another. A campaign can report raw leads while sending a later qualified event to a provider that supports downstream feedback. Provider support, consent rules, and event windows vary, so verify the destination’s contract before enabling delivery. Tracked’s conversion event mapping and postback backfill guide explains the configuration boundary without changing the business definition for you.

A practical lead-event setup checklist

1. Write the stage contract. Define what counts as lead, qualified, approved, customer, rejected, and reversed. Record who can change each state and when its timestamp starts.
2. Capture the identifier. Test that the original Tracked click ID reaches the form, offer, or lead system as a real value; do not substitute a traffic-source ID such as Google’s gclid or a literal macro.
3. Store the stage outside the tracker. Your advertiser, sales process, or CRM owns qualification. Tracked does not validate contact data, score a lead, or replace that system.
4. Return the event. Send the stored click ID and a stable identity for that event. Use the untyped callback for the configured primary outcome; use the mapped event name for secondary stages. Check timestamp and payout handling for the chosen path.
5. Map and inspect. Map provider names to the campaign’s event categories, then confirm the callback is attached to the expected campaign, page, offer, and click.
6. Test retries and late stages. Repeat a callback and send a separate stage for the same click when your contract allows it. Confirm the report and journey show the intended event without turning a retry into a second conversion.

If the path fails, start at the first missing boundary. A missing qualified event is not proof that the page is weak, and a high raw-lead count is not proof of lead quality. Fix the identifier or callback before changing creative.

Read economics only after event quality is clear

Once the stages reconcile, compare payout or revenue with media cost. Tracked’s page-level profit analysis uses allocated campaign spend; it is not a separate ad-platform invoice for each page. Treat unavailable spend as unknown rather than zero. The media-buying campaign review shows how to keep revenue, spend, and conversion windows comparable.

What Tracked does and does not decide

Tracked attributes supplied events to the click and shows the sequence in reports and journeys. It does not determine whether a person is a good lead, approve an advertiser’s submission, run your CRM, or guarantee that a downstream customer event will arrive. Those decisions remain with the business or network that owns the lead contract.

Frequently asked questions

What is the difference between a raw lead and a qualified lead?

A raw lead is the agreed first action, such as a form submission. A qualified lead has passed a later business or advertiser rule. Keep both events when the qualification decision happens after the click.

Can one click create more than one lead event?

Yes, a click can produce a lead followed by qualified, approved, or customer events. Use a stable ID for each distinct event and retain it across retries. Without an explicit event identity, Tracked’s retry fallback uses fixed 60-second buckets, so it is not permanent duplicate protection.

Does Tracked validate or score my leads?

No. Tracked records and attributes the event data supplied by your configured callback. Your advertiser, network, sales process, or CRM decides whether a lead is valid or qualified.

Should I send raw leads or qualified leads back to an ad platform?

Use the stage the platform and your business can define and return consistently. Many teams report raw leads for visibility and use qualified or converted events for deeper feedback, but the correct choice depends on the provider’s rules and the delay in your funnel.

How do I troubleshoot a missing qualified event?

Check the original click ID, the outgoing lead or offer request, the advertiser’s stored identifier, the callback parameters, the event mapping, and the matched journey. Do not treat a 200 response by itself as proof of attribution.

Start free and connect your first lead-generation campaign in Tracked.