Check what the report is adding together
A form click, an accepted submission and a qualified inquiry are different steps. Several correct events become misleading when added together as new customers. Record event name, conversion action, data source and report column before assessing the total.
One business event may be sent directly to an advertising platform and also imported from analytics as another action. That differs from two network requests fired by one tag. Inspect both the website triggers and account definitions.
Follow a fictional submission
Send one permitted test inquiry in an agreed environment. Record the time and an internal test reference without personal information. Use tag management preview and relevant network requests to identify what triggers each signal.
Try validation failures, server errors, double clicks, retries and a reloaded confirmation where the environment allows it. Verify receipt separately. A network request does not establish that the platform counted a conversion or that an email arrived.
| Observation | Possible cause | Next test |
|---|---|---|
| Two tags after one accepted response | Installation in code and tag management | Inventory installation paths |
| Another signal on reload | A page view is treated as success | Use the agreed event condition |
| One request, two report actions | Direct measurement and separate import | Compare sources and purposes |
| Click counted despite server failure | Incorrect triggering condition | Test rejection without a success signal |
Separate counting rules from deduplication
Google Ads distinguishes its one-or-every conversion setting from transaction IDs used to avoid recounting the same transaction. A counting setting answers a reporting question; it does not repair incorrect events or automatically merge separate conversion actions.
Where an integration uses a transaction ID, it must follow the platform's requirements, remain stable for the same transaction and distinguish genuinely new transactions. Do not hardcode one shared ID. Google Ads, Analytics and other services need not share the same deduplication mechanism; assess each connection separately.
Correct the cause and repeat the test
Record the cause, change, code or container version and expected outcome. Remove a redundant installation only after understanding its role. Repeat the test and check that a genuinely new inquiry can still be recorded.
A correction does not make historical reporting errors accurate. Keep those limitations visible when comparing periods. Bring the record to ImbaHub if you need implementation help. Share account access through an agreed secure method, never passwords in a contact form.