What a local service business should check when conversion totals rise when browser and server events both fire: a QA pass before a campaign goes live
Before a new campaign goes live, a local service business can test the full path with a known record. The test should finish at the business system, not at the browser console.
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.
Run the QA pass
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.