Two actions report the same purchase
A fictional store reports a purchase directly through a Google Ads conversion action and separately imports the corresponding Analytics event as another action. Both actions are included in the relevant bidding goal. A colleague sees two conversions and concludes that two different purchases occurred, because the source systems each contain a transaction identifier. Another traces a controlled example and finds that both records represent the same customer transaction. This written exercise accesses no account and sends no data. It asks the learner to distinguish within-action duplicate handling from two independent action definitions, explain why reported volume can become inflated, and propose an accountable configuration review rather than silently deleting all historical records.
1. What is the supported measurement concern?
Read the worked answer
The same business purchase can be represented by two separate included conversion actions. An identifier does not automatically merge every separately configured action.
2. What should the review do?
Read the worked answer
Trace the known transaction, verify the intended goal and action settings, choose appropriate primary/secondary usage, test the resulting reporting and document the authorized change.