Does your report count the same enquiry twice?
When the report grows faster than received enquiries, first check what conversion means. A click, an accepted submission and a sale are different events. Duplication can arise from the technical implementation or from combining several actions in a report.
Trace one enquiry with its own reference
Make an identifiable test and follow it from the form through delivery and measurement. Record when each event occurs. An event on click followed by another on success suggests overlap. Reloading the thank-you page is also useful: observe whether an old enquiry is counted again as new.
Inventory installation points
List tags in code, the tag manager, plugins and the form provider. The same measurement may have been installed twice. Then check whether the report combines actions with similar meanings, such as a direct Ads conversion and an imported event. Document each action's purpose before removing settings.
- Each event's name and source.
- The exact moment it fires.
- The conversion action receiving it.
- Applied consent conditions.
- Its relationship to the enquiry or transaction record.
Give each real event an identity
Google Ads can deduplicate the same action using a unique transaction identifier. That value should identify one occurrence, not the entire application. A fixed identifier can suppress legitimate conversions; generating a new value for every retry does not represent the same enquiry. Define where the identifier originates and how retries reuse it.
Test commonly missed cases
Include double clicks, validation failures, network errors, retries and returns to confirmation pages. A failed enquiry must not appear as success. Compare operational records with measurement while accounting for delays and attribution differences. Record the repair date so a reduction in duplicates is not mistaken for a sudden drop in demand.
Frequently asked questions
Must Ads and GA4 show identical totals?
Not necessarily. Attribution models, definitions, windows and consent can create differences. First confirm each system receives the intended events.
Can a click event remain?
Yes, as an interaction signal. Distinguish it from a confirmed enquiry rather than presenting it as an equivalent received lead.
Reference documentation
A note from ArqWeb
This guide organises checks and decisions for a common situation. Implementation depends on the website, access and systems involved. We can assess your situation if you need help applying these steps.
Let's look at your situation.
Tell us what you need and what you have already. We will reply with next steps and a proposal suited to the work.
Discuss my requirements