Set up new customer acquisition parameter in your conversion tracking tag

The new customer acquisition goal allows you to optimize for acquiring new customers in your Google Ads campaign. In this article, we’ll let you know how to set up new customer acquisition reporting using tagging to further improve the accuracy of new customer detection in your campaigns. Learn more About the new customer acquisition goal.

Note: You must first set up a new customer acquisition goal before enabling new customer acquisition reporting.

Shopify advertisers

We strongly recommend Shopify advertisers install the Google-developed Google & YouTube app. This app automatically implements the necessary Google tracking code on your Shopify store, eliminating the need for manual tagging. It also automatically identifies new customers based on whether it is their first order in the Shopify store, simplifying your implementation. If you have directly implemented Google tag or Google Tag Manager on Shopify, learn more about Migrating your Google tags with the Google & YouTube app on Shopify.

Instructions to set up customer acquisition reporting

Install with the Google tag

Note: To use this option, you must have a "Purchase" conversion action set up in Google Ads that meets certain specifications, and set up customer acquisition in your account. Learn more About the new customer acquisition goal.

Step 1: Install the Google tag conversion tracking code on your website

Review Set up conversion tracking for your website to install conversion tracking with the Google tag.

Note: Only Google Ads conversion tracking biddable purchase conversions can be used for the new customer conversion goal. You won’t be able to track new customers with Google tag for Floodlight or Google Analytics.

Step 2: Add the new_customer parameter to your tag event snippet

You’ll want to add the following customer parameter to your event snippet:

Parameter Value type Description
new_customer Boolean: True / False / [Not specified] Is the customer who is converting a new customer?
  • True: New customer who hasn't purchased within a given time period (540-day lapse window recommended and set at default, but not required).
  • False: A returning customer who has purchased during the given time period.
  • Not specified: If there's uncertainty (for example, use of guest checkout).

Example of the Google tag configured with the above parameter:

<script type="text/javascript">

gtag('event', 'purchase', {

"send_to": "AW-CONVERSION_ID/CONVERSION_LABEL", /* PLEASE REPLACE WITH YOUR VALUE */

...

"new_customer": true, /* calculate dynamically, populate with true/false */

...

]

});

/* ]]> */

Install with Google tag manager

Use the following instructions to add the new_customer parameter to your Google Tag Manager code

  1. Select the new customer conversion tag.
  2. Check the “Provide new customer data” check box.
  3. Choose your data source of either Data Layer or Custom Fields.
  4. The below variables are required to be added on the checkout page to be referenced.
Parameter Value type Description
new_customer Boolean: True / False / [Not specified] Is the customer who is converting a new customer?
  • True: New customer who hasn't purchased within a given time period (540-day lapse window recommended and set at default, but not required).
  • False: A returning customer who has purchased during the given time period.
  • Not specified: If there's uncertainty (for example, use of guest checkout).
customer_lifetime_value Currency

Is the customer lifetime value attributed to the customer making the conversion a new customer?

  • True: If the new_customer parameter is marked “True”, currency value is reported in Google Ads.
  • False: If the new_customer parameter is marked “False”, currency value isn’t reported in Google Ads.

The data layer is used to temporarily hold data. It’s a structured format that is understood by Tag Manager to make it easy for you to move that data from your web page or mobile app to tags, triggers, and other variables in Tag Manager.

You don't necessarily need to set up a data layer for variables to retrieve information. Tag Manager Variables can also be configured to retrieve values directly from Custom Fields, first-party cookies, and the DOM. However, the best practice is to have your variables retrieve information directly from a well-organized data layer object. A data layer implementation can minimize the likelihood of data loss from inadvertent code changes, encourage a well-organized and accessible data model, and simplify troubleshooting.

For each conversion, you can either let Google auto-detect whether a conversion is new or report this yourself via the conversion tag which would allow for better accuracy in your Google Ads reports. You can also adjust how much you value a new customer by adding a fraction of the average order value to their first purchase.

Customer lifetime value is calculated using the average conversion value for Shopping campaigns and the purchase frequency of your customers. Keeping this in mind, you can choose a fraction to determine the new customer value that you feel comfortable with.

Example implementation with Data Layer:

dataLayer.push({

"event": 'purchase',

"transaction_id": "1545c34e-691e-4726-aeda-b798df255e9c",

"affiliation": "Google online store",

"value": 23.07,

"currency": "USD",

"new_customer": true,

});

Example implementation with Custom Fields:

<script type="text/javascript">

send_to = 'AW-CONVERSION_ID/CONVERSION_LABEL'; /* PLEASE REPLACE WITH YOUR VALUE */

transaction_id = "1545c34e-691e-4726-aeda-b798df255e9c";

affiliation = "Google online store";

value = 23.07;

currency = "USD";

new_customer = true;

</script>

Note: Create a User-Defined Variable in Tag Manager for Tag Manager to reference.

Install with Firebase

If you’re using Google Tag Manager currently, you can continue to use Tag Manager with Firebase for Android or iOS. The following steps explain set up and verification of Firebase conversion tracking.

Step 1: Set up Firebase conversion tracking

  1. Add Google Analytics to your Android or iOS app.
  2. Sign in to your Google Ads Account.
  3. Link your Google Ads account with Google Analytics App and Firebase. Follow the instructions on linking.
  4. Measure app conversions from Google Analytics App using the Firebase SDK. Follow the instructions on measuring app conversion with Firebase.
Note: To measure conversions with Firebase, you must use the new SDK, Android 17.3 and iOS 6.2, or later.

Step 2: Verify conversion action settings

In order to track new customer acquisitions, you’ll want to verify that you've correctly set up the conversion action. Map your conversion action settings to the following:

  • Make “conversion action category” equal to “purchase”.
  • Make the “Firebase event” equal to “purchase”.
  • Make the “source” equal to “Firebase”.
  • Make your conversion actions “biddable” (primary conversion action).

Step 3: Add the new_customer parameter to your purchase event

Before you add the new_customer parameter, you have to update the purchase event. If you haven’t created a purchase event yet, follow the instructions for Android and for iOS. The new_customer parameter listed below is required for new customer acquisition tracking using Firebase.

Parameter Value type Description
new_customer Boolean: True / False / [Not specified] Is the customer who is converting a new customer?
  • True: New customer who hasn't purchased within a given time period (540-day lapse window recommended and set at default, but not required).
  • False: A returning customer who has purchased during the given time period.
  • Not specified: If there's uncertainty (for example, use of guest checkout).

Example of a Firebase ecommerce_purchase event driven by a new customer.

Android:

// Prepare ecommerce bundle

Bundle ecommerceBundle = new Bundle();

// Set relevant bundle-level parameters

// New customer information. Should be calculated dynamically and populated with true/false.

ecommerceBundle.putBoolean( "new_customer", true ); // or false

ecommerceBundle.putDouble( Param.VALUE, 37.39 ); // Revenue, optional

ecommerceBundle.putString( Param.CURRENCY, "USD" ); // Optional

// Log event with ecommerce bundle

mFirebaseAnalytics.logEvent( Event.PURCHASE, ecommerceBundle );

iOS:

// Prepare ecommerce dictionary

NSDictionary *ecommerce = @{

// New customer information. Calculate dynamically, populate with @YES/@NO.

@"new_customer" : @YES, // or @NO

// kFIRParameterValue : @75.98, // Revenue, optional.

// kFIRParameterCurrency : @"USD", // Optional.

};

// Log ecommerce_purchase event with ecommerce dictionary.

[FIRAnalytics logEventWithName:kFIREventPurchase

parameters:ecommerce];

Test new customer conversions

Confirm that you're using the Google tag and that you've installed the new_customer parameter.

Use Tag Assistant to confirm if the parameters are being passed (Recommended):

  1. Go to Summary within the Goals menu Goals Icon.
  2. Select View all conversion actions.
  3. In the conversions summary table, check for "Unverified" or "Inactive" statuses in the "Tracking status" column.
  4. Select Troubleshoot in the "Actions" column.
  5. Select Get Started to open the Tag Assistant window. This will open a new window.
  6. Enter the URL of the webpage that you want to troubleshoot. It’s best to use a landing page or home page instead of the conversion page URL directly. Once you visit the landing page, you can navigate to the conversion page.
  7. Select Connect. This will open your webpage in a new browser tab. The conversions summary table and Tag Assistant window will remain open for use later on. Do not close these tabs.
  8. Search for the request that contains your conversion (vndc). The query string parameters should include additional parameters, as shown in the example below:
    • New customers: vdnc: true
    • Returning customers: vdnc: false
  9. Tag Assistant will guide you through the steps to verify the conversion action and provide feedback on each test.
  10. Once you have triggered the conversion actions that you’d like to test, you can select Finish. Or, if you believe you triggered your conversion and Tag Assistant did not show that, you can select I thought I already triggered it.
    • You can select and drag the Tag Assistant badge anywhere on the page, or minimize it, to view and test your webpage.
  11. Once you select Finish, the Tag Assistant badge and your webpage will close. The results of your testing will open in the Tag Assistant window. The results of the troubleshooting page will show the results of the original conversion action you tested, as well as any other conversion action you tested. In this page, you can view additional information about each conversion action that was verified.
  12. Select Close Tag Assistant when you've finished. Tag Assistant will return you to the Google Ads conversions summary page.

Use Chrome Developer tools to inspect the page:

  1. Use Chrome Developer tools to inspect the page to ensure code optimization by following these steps:
    • Select the Chrome menu at the top right corner of your browser window. Select Tools, then select Developer Tools.
    • Right-click on any page element and select Inspect Element. The DevTools window will open at the bottom of your Chrome browser.
  2. In the DevTools window, select Network.
  3. Submit your test order in the web browser.
  4. Search for the request that contains your conversion (search for “/conversion”). The query string parameters should include additional parameters, as shown in the example below:
    • New customers: vdnc: true
    • Returning customers: vdnc: false

Test new customer conversions with Firebase

Confirm that you're using Firebase and that you've added or adapted the purchase event with the cart data parameters.

Then, you can debug events in Firebase in near real-time. You can also track new customer events in Firebase.

Related links

Was this helpful?

How can we improve it?
Search
Clear search
Close search
Main menu
8998854658605337137
true
Search Help Center
true
true
true
true
true
73067
false
false
false
false
false
OSZAR »