Skip to content
Cloud Services

Lead-level attribution

Individual activation for production projects

Know exactly which source became a lead.

TrackAny.Click connects campaign, click, landing page, session and conversion context so teams can follow a lead from first touch to qualified outcome.

Read the attribution guide Open Cloud workspace
01Campaign
02Click
03Landing page
04Session
05Lead
06Outcome
A measurable chain makes every lead traceable and shows where data coverage ends.

Why dashboards disagree

A click is activity. A qualified lead is an outcome.

Measurement breaks when campaign identity disappears at the landing page or customer outcomes never reconnect to the source.

01

Source detail disappears

Inconsistent campaign names and missing identifiers collapse useful touchpoints into generic traffic.

02

Journeys become totals

Counts cannot explain which sequence of visits and events led to a form or sale.

03

Leads lose acquisition context

Sales sees a new contact but cannot tell which campaign, content or click created it.

Lead measurement model

Preserve the context needed to retrace the result.

TrackAny.Click keeps campaign identity, session order, lead events and customer outcomes connected without hiding incomplete coverage.

  1. Available

    Tag the source

    Use stable campaign and content identifiers across ads, email and social links.

  2. Individual activation

    Observe the journey

    Activate consent-aware measurement for the customer project and capture the ordered path.

  3. Individual activation

    Define the lead

    Mark form submission, qualified lead and later commercial outcomes as distinct events.

  4. Individual activation

    Trace the result

    Inspect which source, click, landing page and session contributed to the lead.

Practical exampleLead context example
{
  "campaign": "q4-demand",
  "content": "case-study",
  "event": "qualified_lead",
  "outcome": "sales_accepted"
}

Use a documented event vocabulary and activate production collection for the intended customer project before sending live measurement data.

Questions worth answering

Follow the lead, not just the traffic.

Lead-level context turns channel reporting into a traceable acquisition story.

Which campaign created this lead?

Trace the lead to source, medium, campaign, content and click identifiers.

Read the guide

What happened before the form?

Review the ordered landing pages and events in the session that produced it.

Read the guide

Which leads became real opportunities?

Connect qualified or sales-accepted outcomes to the original acquisition context.

Read the guide

AI-assisted measurement

Give your assistant one lead vocabulary.

A clear campaign convention and explicit event model help assistants instrument journeys consistently across websites and customer flows.

01Create a campaign naming model for every lead source.

Define stable source, medium, campaign, content and identifier rules.

02Instrument our lead journey.

Map landing, session, form, qualification and commercial outcomes in order.

03Explain this lead's acquisition path.

Return the observed touchpoints and show any missing coverage instead of inventing certainty.

Current scope

Measurement designed around traceable leads.

The public script and attribution model are available; production collection and project access are enabled individually.

Available

Public measurement script

Use the published script only with an activated customer project and consent configuration.

↗
Individual activation

Campaign-to-lead journey

Connect campaign and click context with sessions, forms and qualified lead events.

↗
Individual activation

Outcome attribution

Relate later customer outcomes to the lead journey when the required coverage is available.

↗
Planned

Broader provider integrations

Additional advertising and data-source connections are released only after customer availability is confirmed.

↗

A measurable handoff

Keep source context through every lead stage.

Campaign identifiers enter with the click, remain visible through the website journey and connect to qualification and revenue when those outcomes are provided.

01Campaign source
02Click identity
03Website journey
04Qualified lead
05Sales outcome
Reports distinguish observed data from missing or incomplete coverage.
Related products

Responsible measurement

Useful attribution keeps its limits visible.

Consent, data minimization, clear definitions and honest coverage make lead tracking more useful and easier to govern.

Consent-aware setup

Coordinate measurement with the site's consent experience and applicable rules.

Related guide

Minimal campaign data

Keep personal information out of URLs, campaign names and event properties.

Related guide

Explicit lead definitions

Separate submission, qualification, opportunity and revenue instead of calling every action a conversion.

Related guide

Visible coverage

Show what was observed and where attribution data is incomplete.

Related guide

Straight answers

Measure only what the project can support.

Can TrackAny.Click show where a lead came from?

Yes, when campaign identifiers, the website journey and the relevant lead event are measured in an activated project.

Is the public script enough to start?

No. Production measurement also requires an enabled customer project and an appropriate consent configuration.

Does attribution prove causation?

No. It shows the observed path and attribution model. Teams should keep coverage, attribution rules and business context visible.

Make the next lead traceable from the first click.

Define the campaign vocabulary and lead journey, then activate the customer project.