Google Ads guide

How to Set Up Google Ads Conversion Tracking for Ecommerce

To set up Google Ads conversion tracking for ecommerce, define a successful purchase, create a matching conversion action, install one dependable tag and event path, pass transaction ID, value, and currency, control consent and deduplication, and test real checkout branches before trusting reports. Keep cart and checkout events for diagnosis unless the store has a specific reason to use them for optimization.

Start with Google’s web conversion setup guide, then use the order system as the source of truth. The setup is complete only when a test order, Google Ads action, and backend record agree.

1. Define the purchase outcome

Write the event contract before opening the campaign settings. A purchase should mean that the payment and order have reached the successful state the store uses for fulfillment. It should not mean a pay-button click, payment-page view, or confirmation page that can appear after a failed or pending payment.

Decide whether the action covers first orders, subscriptions, renewals, phone orders, or only website transactions. Keep product view, add-to-cart, checkout, and payment-failure events available for funnel diagnosis, but give primary optimization a role that matches the business outcome. Google’s primary and secondary conversion guidance explains this distinction.

2. Create the conversion action

Create or select the Google Ads conversion action with a clear name such as “Store purchase.” Set category, value approach, currency, count behavior, and primary or secondary role according to the event contract. Do not create separate actions for the same purchase merely because different tools can report it.

If the store sells several products with materially different values, pass the transaction value dynamically. If the store can calculate contribution margin reliably, document whether the optimization value is revenue or a margin-based value. Do not send made-up fixed values that make campaigns look efficient.

3. Install the Google tag foundation

Choose an implementation the store team can maintain. Google’s Google tag setup guidance describes the sitewide foundation, while the web conversion setup guide covers web actions. Use the store’s tag manager or integration only when it preserves the agreed event name, value, currency, and transaction ID.

Record the tag location, event trigger, owner, consent behavior, and deployment version. Search for other purchase implementations before adding a new one. A store integration, analytics import, tag manager event, and custom script can all describe the same order.

4. Fire purchase at the right boundary

Trigger the event after the order has a successful status and the order ID is available. For a processor redirect, test successful, pending, declined, cancelled, retried, and refunded outcomes. For account and guest checkout, confirm that both paths use the same event contract.

Use a stable transaction ID from the backend, not a random value generated on each page load. Make a confirmation reload harmless. If a user returns to the page later, the event should not create a second purchase. If an order is reversed, decide whether the source system and Google Ads value will reflect it.

5. Pass value, currency, and product context

Pass the value and currency that the store intends to use for bidding and reporting. Verify tax, shipping, discount, exchange rate, and refund treatment. Keep the source of each field in the event specification. Compare the event with the order database so a test order with a discount or multiple items does not silently pass an incorrect amount.

If product or market reporting matters, preserve that context in the commerce system and analytics layer. Do not place raw customer details into ad hoc debugging output. If Enhanced Conversions is used, follow Google’s Enhanced Conversions best practices and the organization’s privacy process.

6. Configure consent and duplicate control

Review the consent banner, regional rules, tag behavior, and data collection with the site or privacy owner. Test an accepted and refused consent path where the organization permits it. A tag should not bypass the store’s documented consent decision.

List every system that can report purchase. Decide which one is authoritative, which one is diagnostic, and how transaction IDs or another control prevents duplicates. Keep this decision in the measurement inventory. Do not assume that two tools will deduplicate simply because they use similar order names.

7. Test the full checkout

Use Tag Assistant’s guidance and a controlled order to check the event. Verify the click attribution path, conversion action, one firing, transaction ID, value, currency, consent, and backend order record. Cancel or refund the test order according to the store’s normal procedure.

Test the following branches:

  • guest and logged-in checkout;
  • mobile and desktop payment;
  • a declined, pending, and successful payment;
  • confirmation reload and back-button behavior;
  • discount, tax, shipping, and currency differences;
  • consent accepted and refused where testable;
  • a refund, cancellation, or subscription renewal if relevant.

Fix the event contract or implementation before changing bids. A test order proves the path under that condition; it does not explain historical drift.

8. Reconcile the first reporting period

Compare Google Ads purchases and value with accepted orders in the store. Explain differences from attribution windows, time zone, click eligibility, consent, refunds, reporting delay, and offline or phone orders. Investigate missing, duplicate, or unusually high-value transactions before optimization.

Choose a recurring owner for this reconciliation. The first clean report is a baseline, not a guarantee. Recheck after checkout, payment, theme, feed, consent, tag, or analytics changes.

Common ecommerce setup mistakes

  • Firing purchase on a click or page view rather than confirmed order success.
  • Omitting or regenerating transaction IDs.
  • Counting the same order through multiple integrations.
  • Passing a fixed or wrong value and currency.
  • Ignoring consent, refunds, returns, cancellations, or payment failure.
  • Testing only a successful desktop checkout.
  • Changing campaign bids at the same time as tracking, so the cause of a change cannot be isolated.

Keep a versioned event specification and order-level test record to avoid them.

Ecommerce setup checklist

The setup is ready when the purchase boundary, action role, Google tag, event, transaction ID, value, currency, consent, deduplication, test branches, order reconciliation, and owner are documented. For the broader framework, see Best Google Ads Conversion Tracking for Ecommerce. The Google Ads conversion tracking checklist covers general verification, and adz.so can organize account evidence and workflow. It does not replace the store’s order system or privacy review.

Sources