Let’s Build Something Great
Tell us about your goals and request a free project estimate.

Measuring the effectiveness of online advertising requires more than tracking clicks and website visits. Google Ads conversion tracking helps businesses understand which advertising interactions lead to valuable customer actions, from completed purchases and checkout initiations to lead submissions and registrations.
Google Tag Manager provides a centralised way to manage these tracking events, while the Google tag, gtag.js and Google Analytics 4 offer additional measurement capabilities. Understanding how these technologies work together helps ecommerce businesses collect accurate conversion data, evaluate campaign performance and build relevant remarketing audiences.
Advertising performance cannot be evaluated reliably by counting website visits alone. A campaign may attract thousands of visitors without generating meaningful sales, enquiries or registrations.
Conversion tracking helps businesses measure what visitors do after interacting with an advertisement. It connects measurable customer actions with advertising activity, allowing advertisers to evaluate campaign performance and make informed optimisation decisions.
A conversion is an action that an advertiser considers valuable. For an ecommerce store, this usually means a completed purchase. Other useful actions include adding products to a cart, starting checkout, submitting a lead form or creating an account.
These actions represent different stages of the customer journey. Tracking them separately provides more information than measuring completed purchases alone.
Conversions can be divided into two broad groups:
For example, an ecommerce visitor may follow this sequence:
Each action provides a different measurement point. When these interactions are tracked correctly, advertisers can identify where visitors progress and where they abandon the purchasing process.
A cart addition is not equivalent to a sale. A checkout initiation does not establish that an order was completed. Conversion definitions must reflect the actual business outcome being measured.
Google Ads is Google’s online advertising platform. Businesses use it to promote products and services across Google’s advertising inventory and partner properties.
Google Ads was previously called Google AdWords. Google announced the change in June 2018 to reflect the expansion of its advertising products beyond keyword-based search advertising. The current product name is Google Ads.
The platform supports several campaign types, each with different placements and advertising formats.
| Campaign type | Advertising environment | Typical objective |
|---|---|---|
| Search | Google search results | Reach people actively searching for products or services. |
| Display | Websites and applications within the Display Network | Increase visibility and reach relevant audiences. |
| Shopping | Product listings across Google surfaces | Promote products with images, prices and store information. |
| Video | YouTube and other video placements | Build awareness, consideration or drive conversions. |
| Demand Gen | Visual placements across Google’s consumer platforms | Generate demand through visual advertising. |
| Performance Max | Multiple Google advertising channels | Optimise campaign performance across Google’s inventory. |
The available placements and campaign objectives vary by campaign type. Conversion tracking provides the measurement layer used to evaluate the actions generated by these campaigns.
These terms describe different stages of advertising measurement.
An advertising click does not automatically create a conversion. A website session does not establish that the advertisement generated a sale.
Conversion attribution attempts to associate a recorded conversion with an eligible advertising interaction according to the configured attribution model, conversion window and measurement signals.
This distinction is important when interpreting campaign performance. A conversion record shows that a measurement system attributed an action to advertising activity. It does not independently prove that the advertisement was the only factor responsible for the customer’s decision.
A conversion action is a specific activity that Google Ads measures because it has business value.
Examples include:
Conversion actions are organised into conversion goals. Advertisers can decide which actions contribute to campaign optimisation and which should remain available for observation.
Google Ads supports multiple conversion categories, including Purchase, Add to Cart, Begin Checkout, Submit Lead Form and Sign-Up.
Reference: Google Ads conversion categories.
Google Ads, Google Analytics 4 and Google Tag Manager use different terminology because they perform different functions.
Google Ads uses conversion actions to classify and measure valuable customer activities. GA4 uses events to record interactions. Google Tag Manager uses tags, triggers and variables to manage when tracking instructions execute.
The following table shows how the five supported actions relate to their corresponding GA4 recommended events.
| Google Ads conversion category | GA4 recommended event | Purpose |
|---|---|---|
| Purchase | purchase | Measures completed purchases. |
| Add to Cart | add_to_cart | Measures successful cart additions. |
| Begin Checkout | begin_checkout | Measures checkout initiations. |
| Submit Lead Form | generate_lead | Measures successful lead submissions. |
| Sign-Up | sign_up | Measures completed registrations. |
These names are not interchangeable.
For example, purchase is a GA4 event name. Purchase is also a Google Ads conversion category. A GTM implementation may use a third name for its internal custom event trigger, depending on the event structure provided by the website.
GA4 also distinguishes between ordinary events and key events. An event becomes a key event when it represents an important business outcome selected for measurement.
Recommended GA4 events require implementation. They are not automatically generated simply because a visitor performs an interaction on the website.
Source: GA4 recommended events.
Consistent event naming makes it easier to maintain tracking implementations and compare data between systems.
For example, if a website sends a purchase event to GA4 but exposes a separate custom event called order_complete to GTM, the implementation must explicitly map these events to their respective destinations.
A tracking extension may provide a defined set of conversion actions, but the actual event names, parameters and delivery mechanism must be verified against its implementation.
Do not assume that an extension uses GA4 recommended event names internally just because its supported conversion actions correspond to the same customer activities.
The five supported conversion actions cover several important interactions across an ecommerce and lead generation journey.
Purchase is the primary ecommerce conversion for many online stores.
It records a successfully completed order and provides information about the transaction and products purchased.
Relevant information includes:
The event should represent a successfully completed order according to the store’s payment and order-processing logic.
Tracking a checkout button click is insufficient. The website should only report the purchase after the order has been successfully created and reached the appropriate completion state.
A unique transaction ID also helps prevent duplicate purchase reporting.
Add to Cart measures when a customer successfully adds a product to the shopping cart.
This event helps advertisers understand which advertising interactions generate product interest and purchasing intent.
Relevant parameters include:
The event should fire after the cart update succeeds.
This is particularly important for ecommerce stores that update their carts through AJAX without reloading the page. A button click may trigger a request that subsequently fails, so the tracking event should reflect the confirmed cart operation.
Begin Checkout measures when a customer starts the checkout process.
The event identifies visitors who have progressed beyond product selection and cart management.
Relevant information may include:
This event does not indicate that the customer has entered payment details or completed an order.
It measures the beginning of the checkout process.
Submit Lead Form measures a successfully completed lead generation interaction.
Examples include:
The corresponding GA4 recommended event is generate_lead.
The event should fire when the website successfully receives the submission. It should not fire simply because a visitor opens a form, clicks its submit button or attempts to submit invalid information.
A business may assign an estimated monetary value to a lead for advertising optimisation. This value should represent a defined business estimate rather than an arbitrary number.
Sign-Up measures a successfully completed registration.
For an ecommerce store, this may represent a customer creating an account. Other websites may use it for membership registration or another defined sign-up process.
The corresponding GA4 event is sign_up.
An optional method parameter can identify the registration method, such as email or a supported social sign-in method.
The event should fire after account creation succeeds, not when a visitor opens the registration page or submits incomplete registration data.
Google provides a website tagging solution called the Google tag. It allows websites to send measurement information to supported Google destinations, including Google Ads and Google Analytics 4.
The terminology can be confusing because the technology has undergone several naming changes.
gtag.js is the JavaScript library used by the Google tag.
It provides functions for configuring measurement destinations and sending events to Google services.
The technology was previously referred to as the Global Site Tag. Google now uses the name Google tag for its unified tagging solution.
A typical website implementation loads the Google tag and configures its destination using a Google Ads ID or a GA4 Measurement ID.
The Google tag provides the common measurement foundation. Additional event instructions determine which specific interactions should be recorded.
In a direct implementation, the website includes the Google tag and sends a conversion event when a defined action occurs.
Google Ads supplies the necessary tracking information when a website conversion action is configured.
The base Google tag is normally installed across the website. A conversion event snippet is then executed when the relevant action occurs.
A simplified example of the base installation is:
<!-- Google tag -->
<script async src="https://www.googletagmanager.com/gtag/js?id=AW-CONVERSION_ID"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag() {
dataLayer.push(arguments);
}
gtag('js', new Date());
gtag('config', 'AW-CONVERSION_ID');
</script>AW-CONVERSION_ID is a placeholder. It must be replaced with the actual Google Ads tag identifier.
The Google Ads conversion event is sent using the conversion event name:
gtag('event', 'conversion', {
send_to: 'AW-CONVERSION_ID/CONVERSION_LABEL',
value: 149.90,
currency: 'EUR',
transaction_id: 'ORDER-1001'
});This example illustrates a purchase conversion.
The send_to parameter specifies the Google Ads destination using the Conversion ID and Conversion Label.
The value and currency parameters communicate the conversion’s monetary value and currency. The transaction_id identifies the specific order.
For a real implementation, these values should be populated dynamically from the ecommerce system.
The Google tag establishes the website’s connection to the measurement destination.
The conversion event snippet tells that tag when to record a specific conversion.
Installing only the base Google tag does not define every ecommerce conversion automatically. The website still needs to provide the relevant conversion instructions.
Both approaches can send Google Ads conversions, but their implementation and maintenance differ.
| Area | Direct Google tag / gtag.js | Google Tag Manager |
|---|---|---|
| Installation | JavaScript configured in the website. | GTM container installed on the website. |
| Event handling | Website code calls gtag() functions. | Website events are received through triggers and variables. |
| Configuration | Mainly managed through website code and Google tag settings. | Managed through the GTM interface. |
| Changes | May require developer involvement. | Many tracking changes can be managed without modifying the website. |
| Event logic | Implemented through JavaScript calls or configured tag behaviour. | Implemented using tags, triggers, variables and consent settings. |
| Maintenance | Website source code must remain consistent. | Centralised tag management provides a separate configuration layer. |
The Google tag and GTM are not competing measurement destinations. GTM can manage the Google tag and other tracking tags from a central container.
When GTM is already managing the Google tag, adding an unnecessary standalone gtag.js implementation can create duplicate configuration or conflicting event delivery.
Comparison: Google Tag Manager versus gtag.js.
Google Tag Manager is a tag management system that allows website owners and developers to deploy and manage measurement tags without directly editing website code for every tracking change.
It separates the website’s event generation from the configuration of tracking destinations.
GTM does not automatically understand every ecommerce interaction. It needs information from the website, an extension or another event source.
Tags contain the tracking instructions that GTM executes.
Examples include:
A tag sends information to its configured destination when its trigger conditions are satisfied.
Triggers define when a tag should execute.
For example, a Custom Event trigger can listen for the purchase event in the data layer.
When GTM detects the matching event, it can execute the Google Ads Conversion Tracking tag associated with that trigger.
Variables retrieve values used by tags and triggers.
A purchase implementation may require variables for:
These values may originate from the data layer, website JavaScript, page information or other supported variable sources.
The data layer is a JavaScript object that allows the website to provide structured information to GTM.
It can contain event names and associated values.
For example, an ecommerce platform may push an event when a customer completes a purchase.
dataLayer.push({ ecommerce: null }); // Clear the previous ecommerce object.
dataLayer.push({
event: "purchase",
ecommerce: {
transaction_id: "T_12345",
// Sum of (price * quantity) for all items.
value: 72.05,
tax: 3.60,
shipping: 5.99,
currency: "EUR",
coupon: "SUMMER_SALE",
customer_type: "new",
items: [
{
item_id: "SKU_12345",
item_name: "Stan and Friends Tee",
coupon: "SUMMER_FUN",
discount: 2.22,
index: 0,
item_brand: "Google",
item_category: "Apparel",
item_list_id: "related_products",
item_list_name: "Related Products",
item_variant: "green",
price: 10.01,
quantity: 3
},
{
item_id: "SKU_12346",
item_name: "Google Grey Women's Tee",
coupon: "SUMMER_FUN",
discount: 3.33,
index: 1,
item_brand: "Google",
item_category: "Apparel",
item_list_id: "related_products",
item_list_name: "Related Products",
item_variant: "gray",
price: 21.01,
promotion_id: "P_12345",
promotion_name: "Summer Sale",
quantity: 2
}]
}
});This is an illustrative GA4-compatible ecommerce event structure. It does not represent a verified payload from a specific extension.
The event contains two important parts:
event identifies the interaction that occurred.ecommerce contains transaction and product information.GTM can detect the event and retrieve the supplied values through Data Layer Variables.
Google documents this mechanism in its data layer and custom event trigger documentation.
Many ecommerce interactions happen without a traditional page reload.
For example, a visitor may add a product to the cart, change its quantity or remove it through an asynchronous request.
Page-view-based tracking may not identify these interactions reliably.
A custom event provides a way for the ecommerce platform to notify GTM that an operation has succeeded.
The event should be pushed after the underlying operation completes successfully.
A native Google Ads conversion implementation typically combines a Google tag, conversion actions, GTM variables and triggers.
The configuration involves several steps.
Create the required website conversion actions in Google Ads.
For the five supported interactions, an advertiser may configure separate actions for:
Each action should have an appropriate conversion category and measurement definition.
The goal is to make each tracked action identifiable in Google Ads reporting.
When configuring a conversion action for GTM, Google Ads provides the identifiers required by the corresponding tag.
The Conversion ID identifies the account.
The Conversion Label identifies the individual conversion action.
When several conversion actions are tracked, their respective labels must be mapped to the correct GTM tags.
Some automatically created conversion actions do not provide a standalone Conversion Label. When using GTM, Google documents the manual website conversion action workflow for obtaining the required identifiers.
Configure the Google tag in the GTM container and associate it with the correct Google Ads destination.
It should load consistently across the website so that the relevant measurement information is available on the necessary pages.
Create the appropriate Custom Event triggers.
For example:
| Event received by GTM | Trigger purpose |
|---|---|
purchase | Detect a completed purchase. |
add_to_cart | Detect a successful cart addition. |
begin_checkout | Detect the beginning of checkout. |
generate_lead | Detect successful lead submission. |
sign_up | Detect successful registration. |
These names are illustrative GA4-style events. The trigger must use the exact event name actually emitted by the website or extension.
Create a Google Ads Conversion Tracking tag for each conversion action that requires separate native measurement.
Map the relevant fields to GTM variables:
For purchase conversions, dynamic values should be retrieved from the completed order.
For cart and checkout events, the value should reflect the intended measurement definition.
For lead submissions and sign-ups, the advertiser can use an assigned conversion value when it has a meaningful business basis.
An important GTM configuration detail is that an empty or undefined Conversion Value field is sent as zero. Dynamic values should therefore be mapped and validated rather than assumed to populate automatically.
Implementation reference: Google Ads conversions in Tag Manager.
Use GTM Preview mode to confirm that:
Publish the GTM container only after the implementation has passed testing.
Conversion tracking becomes more useful when it communicates the correct business values.
Counting purchases alone provides limited information. Passing transaction values and product details helps advertisers understand the monetary results associated with their campaigns.
For GA4 ecommerce events, the value parameter represents the sum of item prices multiplied by their quantities.
Tax and shipping are sent separately.
For example:
| Parameter | Value |
|---|---|
| Product price | €124.90 |
| Quantity | 1 |
| Ecommerce event value | €124.90 |
| Tax | €20.82 |
| Shipping | €4.90 |
| Total customer payment | €150.62 |
The GA4 purchase event should use 124.90 as its item value in this example, with tax and shipping provided through their respective parameters.
Google Ads conversion value may follow a different business valuation policy. A store might choose to report gross revenue, revenue excluding tax, or another consistently defined value.
The article’s important implementation requirement is to define the calculation before configuring the tag.
A transaction ID uniquely identifies an order.
Consider a customer who completes a purchase and reaches the confirmation page. The customer then reloads the page.
If the purchase tracking tag fires again without appropriate duplicate prevention, the same order may be reported more than once.
A unique transaction ID helps Google Ads identify duplicate purchase conversions.
The ID should:
Transaction IDs and GTM trigger conditions solve different problems. Both should be implemented correctly.
Google reference: Use transaction IDs to minimise duplicate conversions.
Conversion tracking also needs information about the advertising interaction that brought a visitor to the website.
Google Ads provides an auto-tagging feature that adds advertising information to destination URLs.
GCLID stands for Google Click Identifier.
When auto-tagging is enabled, Google Ads can append a gclid parameter to the landing page URL.
For example:
https://example.com/product?gclid=AbCdEf123456This identifier allows Google measurement systems to associate website activity with the advertising click.
It can provide information about the campaign and advertising interaction that generated the visit.
Depending on the advertising environment and measurement configuration, other parameters may appear.
These include:
gbraidwbraidgad_sourcegad_campaignidGBRAID is a privacy-preserving identifier used for aggregate advertising measurement rather than identifying individual users or individual events. WBRAID supports privacy-aware advertising measurement in relevant iOS scenarios.
The gad_* parameters can provide aggregate campaign-source information.
These parameters should not be treated as interchangeable with GCLID. They serve different measurement purposes and may appear under different circumstances.
Sources: Google Ads auto-tagging and GA4 aggregate identifiers.
Advertising click information can be lost when a website redirects visitors or modifies landing page URLs incorrectly.
For example, an ecommerce store may redirect a visitor from a campaign landing page to a canonical URL while removing query parameters.
If the redirect removes the relevant advertising identifiers before the tracking tags process them, attribution may be affected.
Website developers should verify that redirects, URL rewriting rules and navigation processes preserve the relevant measurement parameters.
UTM parameters are manually configured URL parameters used to identify traffic sources and campaign information.
For example:
https://example.com/product
?utm_source=google
&utm_medium=cpc
&utm_campaign=spring_saleGCLID is automatically generated by Google Ads when auto-tagging is enabled.
UTM parameters provide manually defined campaign information. GCLID provides a Google advertising click identifier with more detailed click-level measurement capabilities.
They serve related but different purposes.
Using UTM parameters does not automatically replace Google Ads auto-tagging.
Conversion tracking and remarketing are connected, but they measure different things.
Conversion tracking measures valuable actions.
Remarketing allows advertisers to reach people who previously visited a website or interacted with its content.
Google increasingly uses the term data segments for website visitor audiences. Older documentation and industry terminology commonly refer to remarketing lists.
A visitor arrives at an ecommerce website and interacts with its products.
A compatible Google Ads remarketing implementation records the relevant website activity, subject to the applicable consent and advertising settings.
The visitor may subsequently become eligible for an audience segment based on the configured conditions.
For example, a store can create segments for:
Advertisers can then use eligible audience segments in supported Google Ads campaigns.
Standard remarketing uses website visitor information to create audiences.
An advertiser might target people who previously visited a product category but did not complete a purchase.
Standard remarketing does not inherently require a product feed.
It primarily depends on website tagging, audience conditions, membership settings and campaign configuration.
GTM can deploy the Google Ads Remarketing tag. The tag is generally placed across the website so Google can measure relevant visits and build eligible audience segments.
The implementation may also provide additional event information when visitors perform important actions. For example, the website can provide product information when a customer adds a product to the cart.
Reference: Google Ads remarketing with Tag Manager.
Dynamic remarketing extends standard remarketing by allowing advertisements to display information about products or services that visitors previously viewed or interacted with.
The advertising content can be selected using website interaction data and a corresponding product or business data source.
Retail dynamic remarketing uses product information from Google Merchant Center.
The implementation requires:
The product identifiers transmitted by the website must match the corresponding identifiers in the product feed.
For example, if the website sends a product identifier that does not match the Merchant Center item ID, Google may not be able to associate the visitor’s interaction with the intended product.
Relevant information may include:
Non-retail businesses can also use dynamic remarketing.
Examples include travel, education, accommodation and other service-based businesses.
These implementations use business-specific data sources or asset sets rather than necessarily relying on a retail Merchant Center feed.
The event parameters and feed requirements depend on the relevant business vertical.
Dynamic remarketing should therefore not be treated as a single universal product implementation.
Recording a purchase or cart addition does not automatically configure dynamic advertisements.
Dynamic remarketing requires the appropriate remarketing tag, event information, identifiers and feed or business data configuration.
A website may already have correctly configured Google Ads conversion tracking while having no dynamic remarketing implementation. These are separate configurations.
An additional distinction concerns GA4. GA4 audiences can be shared with linked Google Ads accounts, but Google documents that dynamic remarketing for web is not supported by GA4 properties. A separate Google Ads dynamic remarketing implementation is required for that specific functionality.
Sources: Google Ads dynamic remarketing in GTM, Dynamic remarketing for retail, and Google Ads audience sources.
The five supported conversion actions can provide useful signals for audience segmentation when the required event information is available to Google Ads or GA4.
Each event represents a different stage of customer interaction.
| Event | Potential audience application |
|---|---|
| Purchase | Create previous-purchaser audiences and exclude existing customers from selected acquisition campaigns. |
| Add to Cart | Identify visitors who added products but did not complete a purchase. |
| Begin Checkout | Identify visitors who initiated checkout but did not complete an order. |
| Submit Lead Form | Create audiences based on successful lead submissions. |
| Sign-Up | Identify registered users for suitable follow-up campaigns. |
Audience conditions can combine included and excluded actions.
For example:
Add to Cart AND NOT Purchase
This condition identifies visitors who added products to their carts but did not complete a purchase within the defined audience rules.
Another example:
Begin Checkout AND NOT Purchase
This identifies visitors who entered checkout but did not complete an order.
A business may also create a previous-purchaser segment and exclude that audience from selected new-customer acquisition campaigns.
Audience membership duration and eligibility must be configured in accordance with the relevant Google Ads settings and policies.
The five supported events do not include product-view tracking.
GA4 uses the recommended view_item event to measure when a visitor views a specific product.
If a store wants to build product-view audiences or use product-view information for dynamic remarketing, it needs an appropriate product-view tracking implementation.
The presence of Add to Cart or Purchase events does not establish that product-view tracking is supported.
This distinction matters when defining the actual scope of an ecommerce tracking extension.
A reliable tracking implementation involves several connected components.
Each component has a separate responsibility.
| Component | Responsibility |
|---|---|
| Ecommerce platform | Processes customer interactions and transactions. |
| Tracking extension | Provides or supports the required tracking events. |
| Website event generation | Identifies when an action has successfully occurred. |
| JavaScript data layer | Provides structured event information to GTM. |
| Google tag / gtag.js | Provides Google’s website measurement connection. |
| Google Tag Manager | Manages tags, triggers, variables and tag execution. |
| GA4 | Collects and reports website and ecommerce events. |
| Google Ads Conversion Tracking | Measures configured advertising conversion actions. |
| Google Ads Remarketing | Collects website interaction information for eligible audiences. |
| Conversion Linker | Preserves advertising click information for measurement. |
| Google Analytics audiences | Groups users according to configured audience conditions. |
| Google Merchant Center | Supplies product information for retail Shopping and dynamic remarketing integrations. |
Consider a customer who clicks a Google Search advertisement and purchases a product.
The tracking process can follow this sequence:
A separate remarketing implementation may also use eligible website interactions and dynamic product parameters to build audience segments.
Not every installation uses all these components in exactly the same way. Direct gtag.js tracking can send Google Ads conversion events without using GTM as the event-management layer.
A. Direct Google tag implementation
The website uses the Google tag and sends Google Ads conversion event commands through gtag.js.
The ecommerce platform must provide the relevant event values and trigger the conversion call at the correct time.
B. Google Tag Manager implementation
The ecommerce platform or extension generates events and provides them to GTM through the data layer or another supported mechanism.
GTM uses triggers and variables to execute Google Ads, GA4 or remarketing tags.
C. GA4-based conversion import
The website sends recommended events to GA4. Important events can be designated as key events, and selected events can then be used to create Google Ads conversion actions through the linked accounts.
These approaches are related, but they are not interchangeable.
A business should select its measurement architecture deliberately. Running multiple implementations for the same conversion action without defining their roles can produce duplicate records or inconsistent reporting.
Reference: Link Google Analytics 4 and Google Ads.
Conversion and remarketing tracking must respect the visitor’s consent settings and the applicable privacy requirements.
Google Consent Mode allows websites to communicate consent choices to Google tags.
It does not provide a cookie consent banner or replace a consent management platform. Instead, it communicates the choices made through the website’s consent mechanism and adjusts tag behaviour accordingly.
| Consent signal | Purpose |
|---|---|
ad_storage | Controls advertising-related cookie storage. |
analytics_storage | Controls analytics-related cookie storage. |
ad_user_data | Controls consent for sending user data related to advertising. |
ad_personalization | Controls consent for personalised advertising. |
Basic Consent Mode prevents Google tags from loading until the user interacts with the consent mechanism and grants the relevant permissions.
Advanced Consent Mode allows Google tags to load with configured default consent states. When storage is denied, supported tags adjust their behaviour and may send cookieless pings.
The implementation must communicate the correct default state before the relevant measurement tags execute and update that state when the visitor makes a choice.
The appropriate setup depends on the website’s consent management implementation and applicable privacy requirements.
Reference: Consent Mode support in Tag Manager.
Enhanced Conversions supplement existing conversion measurement with appropriately formatted first-party customer information.
Depending on the configuration, this can include information such as email addresses or phone numbers.
Google uses SHA-256 hashing for supported customer information before matching it with signed-in Google accounts for conversion measurement.
Enhanced Conversions require an appropriate implementation, customer data handling and compliance with Google’s applicable policies.
They are an optional measurement enhancement. They are not a replacement for basic conversion tracking, a consent mechanism or accurate event implementation.
Google provides separate implementation documentation for the Google tag and GTM.
References: Enhanced Conversions with the Google tag and Enhanced Conversions with Google Tag Manager.
A tracking implementation should be validated before it is published.
A conversion tag appearing in a GTM container does not prove that it is receiving correct values or firing at the right time.
Testing must cover the entire event flow.
GTM Preview mode allows developers to connect Tag Assistant to a website and inspect the events detected by the container.
For each supported conversion, verify:
Inspect the data layer to confirm that the website provides the correct event information.
For example, a purchase event should contain a real transaction ID, the expected value, currency and product details.
An event that contains only a name but no required dynamic values may be insufficient for the intended measurement configuration.
Verify the conversion ID and label associated with each tag.
Confirm that the correct tag fires for each action.
A Purchase event must not trigger an Add to Cart conversion action. A lead submission must not trigger a purchase tag.
Browser developer tools provide another way to investigate tracking problems.
The Network panel can be used to inspect outgoing measurement requests and verify whether the expected information is being sent.
This is particularly useful when GTM Preview indicates that a tag fired but the destination does not appear to receive the expected conversion information.
| Test | Expected result |
|---|---|
| Purchase | Fires after a successfully completed order. |
| Add to Cart | Fires after a successful cart update. |
| Begin Checkout | Fires when checkout actually starts. |
| Submit Lead Form | Fires after successful form submission. |
| Sign-Up | Fires after successful registration. |
| Transaction ID | Uses a unique, consistent order identifier. |
| Conversion Value | Contains the expected dynamic monetary value. |
| Currency | Uses the correct ISO 4217 currency code. |
| Duplicate prevention | Reloading the order confirmation page does not create another purchase. |
| Consent | Tags respect the configured consent state. |
| Attribution | Advertising URL parameters are preserved. |
| Remarketing | Relevant audience tags and parameters are transmitted correctly. |
After testing, publish the GTM container and monitor the conversion diagnostics in Google Ads.
Conversion reporting and status information may not update immediately after implementation.
Google Ads and GA4 do not necessarily report identical conversion totals, even when both systems receive the same underlying website events.
They use different measurement and attribution configurations.
Google Ads generally associates conversions with the date of the advertising interaction that led to the conversion.
GA4 generally reports an event on the date the event occurred.
For example, a visitor clicks an advertisement on November 2 and completes a purchase on November 3.
Google Ads may attribute the conversion to November 2, while GA4 records the purchase event on November 3.
This can create differences when comparing daily reports.
Google Ads provides two principal conversion counting settings.
Every: Counts every qualifying conversion after an advertising interaction. This is generally appropriate for purchases because each separate sale has business value.
One: Counts one conversion after an advertising interaction. This is often suitable for lead generation when repeated submissions should not automatically count as separate business outcomes.
The correct setting depends on the conversion action.
Google Ads distinguishes between primary and secondary conversion actions.
| Configuration | Reporting | Bidding optimisation |
|---|---|---|
| Primary | Included in the Conversions column when its associated goal is used by the campaign. | Used for optimisation when included in the campaign’s bidding goals. |
| Secondary | Normally reported in the All conversions column. | Normally excluded from standard bidding optimisation, subject to custom goal configuration. |
For many ecommerce stores, Purchase is the principal conversion used for bidding.
Add to Cart and Begin Checkout may be kept as secondary actions to provide additional funnel information without treating every cart interaction as a completed business result.
Lead generation businesses may choose Submit Lead Form or another qualified lead action as their primary goal.
When GA4 key events are used as Google Ads conversion actions, reporting differences may also result from conversion counting settings and the systems’ attribution rules.
An event count in GA4 is not necessarily equal to the number of conversions shown in the Google Ads Conversions column.
A difference should be investigated, not automatically treated as evidence of broken tracking.
References:
Several implementation errors occur repeatedly in ecommerce tracking.
| Problem | Likely cause | Recommended investigation |
|---|---|---|
| Purchase conversion does not fire | Incorrect trigger or missing purchase event. | Inspect the order completion process and GTM event timeline. |
| Purchase fires more than once | Confirmation page reloads or duplicate tracking implementations. | Check transaction IDs and all active conversion tags. |
| Conversion value is zero | Variable is missing, undefined or mapped incorrectly. | Inspect the data layer and Conversion Value variable. |
| Currency is incorrect | Static currency configuration or an incorrectly mapped variable. | Compare the event currency with the actual order currency. |
| Add to Cart is missing | Cart update occurs asynchronously and no custom event is generated. | Inspect the successful AJAX response and data-layer events. |
| Lead conversion fires on invalid submissions | Trigger listens to a button click rather than successful form completion. | Use a success event or verified submission response. |
| Sign-Up fires before registration completes | Tracking is connected to the registration form submission rather than account creation. | Trigger after successful account creation. |
| Google Ads cannot attribute conversions | Click identifiers are lost or measurement tags are not configured properly. | Inspect landing page parameters, redirects and tag settings. |
| GA4 and Google Ads figures differ | Different attribution, dates, counting settings or conversion definitions. | Compare the same conversion action and date basis. |
| Remarketing audiences remain empty | Missing remarketing tag, missing parameters or audience configuration issues. | Validate the tag, event information and audience rules. |
The most effective troubleshooting method is to trace the event from the website through the data layer, GTM and the final destination.
Checking only whether a tag exists in the container is insufficient.
Google Ads conversion tracking provides a way to measure how advertising interactions relate to meaningful website activity.
For ecommerce stores, the five supported actions cover important points in the customer journey: purchases, cart additions, checkout initiations, lead submissions and registrations.
Google Tag Manager makes it possible to manage conversion tags centrally, while the Google tag and gtag.js provide direct measurement capabilities. GA4 adds event-based reporting and audience analysis. Google Ads remarketing provides separate functionality for reaching eligible previous visitors.
The reliability of the entire setup depends on accurate event generation, appropriate parameters, correct tag configuration, preserved advertising identifiers, duplicate prevention and consent-aware measurement.
These components should be implemented as a coherent tracking architecture rather than as unrelated tags added to a website.
For an ecommerce business, the objective is to measure real customer actions accurately and provide advertising platforms with consistent information that supports meaningful campaign analysis and optimisation.
Google Official Documentation
Independent Technical Reference
The Analytics Mania article was updated on August 11, 2026. Its practical examples should be interpreted alongside the applicable current Google documentation.
Historical Reference
Playful Sparkle has engineered digital products since 2004. We work across Web Development, Digital Marketing and technical integrations to help businesses build reliable digital systems. Our work includes ecommerce measurement, analytics implementation, advertising conversion tracking and the integration of tracking technologies with website functionality. Accurate measurement starts with the quality of the underlying website events. Tracking should reflect what actually happens in the ecommerce system, not merely what a visitor clicks. For support with ecommerce tracking architecture, Google Tag Manager implementation or digital measurement, contact Playful Sparkle.