How to define and check lead conversion tracking

Map the customer journey before the tags

A visitor can click a phone number without completing a call. Someone can submit a request outside the service area. A qualified inquiry can still decide not to book. Giving all three events the same name hides the difference.

Agree the qualification rule with the business. It might require the correct service, an accepted service area and a genuine request. Keep that rule consistent when comparing periods.

Choose a trigger that matches the name

For a form-accepted event, wait for the form service’s successful response. Do not fire it when the submit button is clicked or when a thank-you panel appears before the request completes. A page reload should not create another accepted request event.

Give each submission a stable identifier where the receiving system supports duplicate handling. Avoid sending a person’s message, email or phone number in ordinary analytics event fields. Any separate advertising data integration needs its own supported setup and applicable consent handling.

Google’s conversion tracking overview explains the platform’s supported conversion sources. Installing a tag does not remove the need to define the underlying action accurately.

Inspect what bidding actually uses

In Google Ads, primary actions can appear in the Conversions column and support bidding when their standard goal is selected. Secondary actions normally support observation through All conversions. There is an important exception: actions in a custom goal can be used for bidding regardless of their primary or secondary label.

Check the campaign’s selected goals as well as the action settings. The primary and secondary action documentation describes this distinction. Marking a weak event secondary is not enough if a custom goal still uses it.

Reconcile a small set of records

Worked example · illustrative, not a client result

Suppose a report shows ten form events, while the receiving system has six distinct requests. Two may be repeated clicks, one may come from a failed request, and another may have an unknown cause. These are investigation possibilities, not explanations to assume.

Compare timestamps and allowed submission identifiers. Reproduce the suspected trigger with mocked responses. Check whether accepted requests appear once and failures appear zero times in the accepted-request count. Keep unresolved differences visible instead of adjusting the count to make the systems agree.

Connect later outcomes when the records support it

Qualified inquiries and bookings usually live in business records after the website visit. Google Ads supports offline conversion imports, but that requires a valid attribution and data-handling setup. It does not happen merely because a CRM contains the outcome.

Start with trustworthy records and a clearly defined goal. Then decide whether a supported import can improve measurement. Keep reporting latency, attribution differences and missing matches in the explanation. Use the cost and contribution calculation to judge what those outcomes are worth.

Continue learning