Where duplicate conversion records appear for a franchise network: what to check before changing the stack
Start with one real record from a franchise network. Capture what the systems already know before you change a setting or add another tool.
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.
Before you change anything
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.