Reviewing duplicate conversion records in a franchise network: a weekly reporting routine
A weekly report is easier to trust when it keeps the same checks each time. This routine gives a franchise network a small set of comparisons to repeat.
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.
Keep the weekly check
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.