Should every interaction be a primary conversion?
No. Review which actions represent the campaign’s real goals and how the actual goal settings use them.
A practical decision guide
A button click, a submitted inquiry and a qualified customer opportunity are different actions. Tracking is useful when those distinctions stay clear. Start with the business event, then check how the account records it.
Write a plain definition: for example, a successful inquiry received by the business, rather than a visit to the contact page. Decide what proves the event and what does not. If qualification happens later, keep that stage separate. Do not label every form submission a customer or every confirmation page view a sale.
List the tags, analytics imports and other routes that may record the action. Check whether two routes describe the same event. Review counting settings and which actions are used in the campaign’s goals. Google Ads distinguishes primary and secondary actions, with special behavior for custom goals, so verify the actual configuration rather than assuming a label tells the whole story.
Use an authorized test with non-sensitive details and a known expected result. Check valid completion, validation errors, repeat clicks and a return to the confirmation page. Note which event should fire in each case. A test should not create an unapproved purchase, booking or misleading operational record.
Identify what information is collected and sent, what disclosures apply and who is responsible for the configuration. Do not put personal details into URLs or event names. Where legal or policy questions arise, resolve them with the appropriate specialist rather than treating a tracking tutorial as legal advice.
Compare a suitable sample of recorded actions with the business system that receives them. Account for reporting delays, attribution settings and the dates being compared. Differences deserve explanation, not automatic dismissal. Keep tests, duplicates, spam, genuine inquiries and later qualified outcomes distinguishable.
A practical tracking handover names the event, source, counting rule, campaign-goal role, test result and known limitation. It should also say who reviews changes when the form or website is updated. A green tag status is useful technical evidence, but it does not replace a check that the business action is represented correctly.
No. Review which actions represent the campaign’s real goals and how the actual goal settings use them.
Only if that action specifically represents a verified qualification event. A submission alone does not.
They may use different counting, attribution or date rules. Compare definitions before deciding which figure is wrong.
Official guidance checked 2026-10-26.
Tell us what you have in mind. A little context is enough to start a useful conversation.