Before a local service business changes its tracking, review duplicate conversion records: as an implementation brief
A useful implementation brief names the source, the destination, the identifier, and the failure response. That keeps a local service business from leaving important decisions inside a chat thread.
Read the symptom
One business action can travel through more than one reporting path. A browser event and a server event may describe the same lead, or a retry may create a second record.
Inspect the path
- List every path that can send the conversion event.
- Find the business record ID shared by the browser, server, and CRM rows.
- Compare event names, timestamps, and status values.
- Test a single known conversion and follow it through each system.
Write the brief
Choose one stable deduplication value and record where it is created. Keep the test result with the record it describes so the next review starts with evidence, not a guess.
If you need a persistent record of the path, see ClickTrail.