Free diagnostic resource

Lead Source Breakpoint Checklist

Test every handoff from the tagged landing URL to the final CRM record. No email required.

How to use it

Choose one real campaign path and one test contact. Save the landing URL, network payload, CRM property history, and screenshots. Mark a step complete only when the value survives into the next system.

01

Landing URL

Open a tagged test URL in a fresh browser session.
Record UTMs, click IDs, landing page, and referrer before navigation.

02

Navigation and storage

Move to a clean URL and confirm the original values remain available.
Repeat after consent is accepted, declined, and changed.
Test the intended expiry and a return visit.

03

Redirects

Check every redirect preserves or deliberately stores campaign evidence.
Test short links, HTTP-to-HTTPS, host changes, and cross-domain steps.

04

Form payload

Inspect the actual request, not only visible hidden fields.
Confirm field names, values, encoding, and empty-value behavior.
Test embedded and cross-origin forms through supported APIs.

05

CRM field mapping

Map each form field to one documented CRM property.
Separate original-touch fields from converting/latest-touch fields.
Test both a new record and an existing record.

06

Workflows and integrations

List every system allowed to write each source field.
Wait for automation to finish, then recheck the record history.
Protect immutable original evidence from later writers.

07

Imports and merges

Import an update without source fields and verify originals survive.
Merge duplicate contacts and confirm the intended source wins.
Check enrichment tools do not replace known evidence with blanks.

08

Re-conversions

Submit again without UTMs and verify original-touch fields remain intact.
Confirm converting-touch fields update only under the documented rule.
Repeat the test after changing forms, consent, redirects, or workflows.

Questions that come up during testing

What counts as a breakpoint?

Any handoff where correct acquisition evidence becomes missing, changed, or unavailable to the next system.

Should original and latest source use one field?

Usually no. One field cannot remain immutable and also describe a later conversion. Use fields with one documented meaning each.

Does a hidden field prove the CRM received the value?

No. Inspect the submitted payload, CRM mapping, and final record after workflows run.

How often should this be repeated?

Repeat after changes to forms, consent, redirects, tag managers, CRM mappings, workflows, imports, or integrations.

Found a breakpoint?

Bring the form and CRM path to a 20-minute workflow review.

Book a workflow review