From an action to a recorded conversion
Text version
- User action
- Tag / event
- Configured conversion
- Ads / Analytics reporting
How it works
Check events, counting, attribution and applicable consent requirements.
Example
Example: A test order confirms the purchase and value are recorded once.
Common mistakes
A functioning tag does not prove correct goals or complete measurability.
How can you check this in practice?
Run the actual journey with a safe test order or form. Check event, transaction id, value, currency and counting on reload. When using both an Ads tag and Analytics import for one purchase, ensure bidding is not optimising towards two records of the same action.
Distinctions and limitations
A tag, event and configured Ads conversion are separate pieces. A successful tag request does not establish correct value or absence of duplication. Consent, window and attribution settings affect recorded counts.
Counting and business meaning
Purchases and leads can need different counting settings depending on the task. Check primary/secondary status and campaign goals. A secondary action can support observation without automatically being a suitable bidding objective.
Duplication example
A thank-you page sends purchase on every reload without transaction id. One order may generate multiple records. Verify confirmed order IDs and repeat actions; visible tag firing does not prove a unique sale.
Official sources
Editorial responsibility: Biser Bozhinov · PPC Specialist
Updated: 05/11/2026
For a correction or question: office@z-consult.bg