{"id":5142,"date":"2022-06-30T17:47:46","date_gmt":"2022-06-30T14:47:46","guid":{"rendered":"https:\/\/trackingchef.com\/?p=5142"},"modified":"2023-02-12T18:23:50","modified_gmt":"2023-02-12T15:23:50","slug":"creating-and-installing-a-google-ads-conversion","status":"publish","type":"post","link":"https:\/\/trackingchef.com\/google-ads\/creating-and-installing-a-google-ads-conversion\/","title":{"rendered":"Creating and installing a Google Ads Conversion"},"content":{"rendered":"\n

In this post, I\u2019ll show how to quickly and efficiently set up a new conversion event for Google Ads. <\/p>\n\n\n\n

The Google Ads pixel uses the same mechanism as other standard pixels<\/a>, so its setup is pretty simple.<\/p>\n\n\n\n

Alongside your conversion tracking, I also recommend implementing Google Ads Global Site Tag<\/a> across your site.<\/p>\n\n\n\n

Creating a Google Ads Conversion<\/h2>\n\n\n\n
\n

Creating conversions can be done only after setting up an active Google Ads account.<\/p>\n<\/blockquote>\n\n\n\n

In your account, use the top menu to navigate to Tools and Settings -> Measurement -> Conversions.<\/p>\n\n\n\n

Conversions in Google Ads can originate from multiple sources:<\/p>\n\n\n\n

    \n
  1. Website – Track conversion events that happened on your site<\/li>\n\n\n\n
  2. App – Track conversion events that happened on your app (Android or iOS)<\/li>\n\n\n\n
  3. Phone calls – Track incoming phone calls to your business using a dynamic phone number<\/li>\n\n\n\n
  4. Import – Conversion events that a brought in from other sources such as Google Analytics or a CRM<\/li>\n<\/ol>\n\n\n
    \n
    \"\"<\/figure><\/div>\n\n\n

    For sake of simplicity, this guide will only cover Website conversions.<\/p>\n\n\n\n

    Goal category<\/h3>\n\n\n\n

    After selecting the Website type, you can select the type of user engagement you want to track, e.g. Purchase or Submit a lead form.<\/p>\n\n\n\n

    This helps Google Ads group similar conversion actions together and make more sense of them.<\/p>\n\n\n

    \n
    \"\"<\/figure><\/div>\n\n\n

    Next, you can select whether the conversion event should be set as a Primary or Secondary conversion.<\/p>\n\n\n\n

    A Primary conversion is our end goal, whereas a Secondary conversion is a step in the way. We won’t want the secondary conversions to be reported in the same manner as the primary nor would we want Google’s optimization algorithms to weigh them the same.<\/p>\n\n\n\n

    In a SaaS example, we can add Sign up as a Secondary conversion and Purchase as a Primary. <\/p>\n\n\n\n

    In an ecommerce example, we can add Add to Cart as a Secondary conversion (by unticking the “add to account default goals” checkbox) and Purchase as Primary.<\/p>\n\n\n

    \n
    \"\"<\/figure><\/div>\n\n\n

    Next, we give the conversion a memorable name that will be easy to comprehend.<\/p>\n\n\n\n

    Event Value and Count<\/h3>\n\n\n\n

    We can then select a value for the conversion. In some cases, we don’t know – a lead for a demo might be worth millions or a few thousand dollars, it’s hard to tell. But in others it’s easier – ecommerce will likely be the sum of the purchase, and SaaS can use a simplistic predicted LTV model.<\/p>\n\n\n\n

    This value can be passed dynamically as part of the event’s code.<\/p>\n\n\n\n

    You can then select whether easy conversion should be counted once per user. A lead form, no matter how many times submitted, is still worth the same if it’s the same user. Multiple ecommerce transactions by a single user are indeed the sum of all these.<\/p>\n\n\n

    \n
    \"\"<\/figure><\/div>\n\n\n

    Attribution<\/h3>\n\n\n\n

    Last, but not least, you can tweak various attribution related settings. I usually keep these as is for most clients I work with.<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    A note on importing conversions from Google Analytics<\/h2>\n\n\n\n

    While you can easily import your existing Google Analytics goals to be used as conversion events in Google Ads, in most cases I won’t recommend this.<\/p>\n\n\n\n

    There are many reasons for this, you can read about them in depth in this great post <\/a>by Julian Juenemann. My main concern is that Google Analytics uses a Last In-Direct click attribution model and that its tracking is less accurate than Google Ads due to its cookie limitations.<\/p>\n\n\n\n

    So if you have the technical option to add Google Ads conversions I highly recommend you do so.<\/p>\n\n\n\n

    Manually installing the Google Ads Conversion<\/h2>\n\n\n\n

    After you’ve saved the conversion you can choose how you want to install it on your site.<\/p>\n\n\n\n

    Installing the conversion manually requires first triggering the Global Site Tag<\/a>. Assuming that tag has been implemented, you will be able to trigger your conversion event.<\/p>\n\n\n\n

    The event’s script should look something like this:<\/p>\n\n\n\n

    <!-- Event snippet for Demo Request conversion page -->\n<script>\n  gtag('event', 'conversion', {'send_to': 'AW-1234567890\/abcdefghijklmnop'});\n<\/script>\n<\/code><\/pre>\n\n\n\n

    In the event snippet, you can find two IDs. The first is the tag ID (e.g. AW-1234567890) which is identical to the one used on the Global Site Tag. The second, referred to as the Conversion Label (e.g. abcdefghijklmnop), is used to identify the specific conversion action. For example, your site might have both a Demo form and a Sign Up form, and you will likely want to measure these separately.<\/p>\n\n\n\n

    Trigger this JS function whenever the conversion event happens.<\/p>\n\n\n\n

    Adding conversion value<\/h3>\n\n\n\n

    If the conversion has a clear monetary value you can assign a conversion value using a parameter in the event. You can also set the currency in which you’re reporting, otherwise it will default to the account’s currency (reporting will in any case convert the value to the account’s currency).<\/p>\n\n\n\n

    gtag('event', 'conversion', {'send_to': 'AW-1234567890\/abcdefghijklmnop','value': 1.0, 'currency': 'USD'});<\/code><\/pre>\n\n\n\n

    Adding custom variables<\/h3>\n\n\n\n

    You can also add custom parameters to report on more granular conversions. For example, if you are running ads for a hotel chain with multiple locations, you can add a parameter that passes the name if the specific hotel the conversion was for.<\/p>\n\n\n\n

    You can read more in this post about Google Ads Custom Variables<\/a>.<\/p>\n\n\n\n

    Installing a Google Ads Conversion using Google Tag Manager<\/h2>\n\n\n\n

    Similar to other major platforms, Google Ads has a built-in tag in Google Tag Manager.<\/p>\n\n\n\n

    When creating the conversion, you can choose to install it using Google Tag Manager. This option will give you the relevant Conversion ID and Conversion Label values to use in GTM.<\/p>\n\n\n

    \n
    \"image-5472759\"
    Getting the Conversion ID and Label in GTM<\/figcaption><\/figure><\/div>\n\n\n

    First, copy the Conversion ID. It should look something like this 1234567890<\/em> (without the AW-<\/em> prefix).<\/p>\n\n\n\n

    \n

    Pro tip:<\/strong>
    Since the Conversion ID is an account wide ID, it will be the same for all your account’s conversions. That’s why I recommend saving it as a Variable of the type Constant so you can reuse it in new Google Ads conversions you create.<\/p>\n<\/blockquote>\n\n\n\n

      \n
    1. Go to your GTM account and open the relevant container<\/li>\n\n\n\n
    2. Click \u201cAdd a new tag\u201d<\/li>\n\n\n\n
    3. Name the tag something memorable, e.g. Google Ads Demo Request<\/li>\n\n\n\n
    4. Under Tag Configuration select \u201cGoogle Ads Conversion Tracking\u201d
      <\/li>\n<\/ol>\n\n\n
      \n
      \"\"<\/figure><\/div>\n\n\n
        \n
      1. In the Conversion ID field, paste the Conversion ID you copied, e.g. 1234567890<\/li>\n\n\n\n
      2. In the Conversion Label field matching value from your Google Ads account, e.g. abcdefghijklmnop<\/li>\n\n\n\n
      3. Under Triggering, choose a new trigger. This trigger will depend on the specific user action you want to track as a conversion (e.g. a lead form submission).<\/li>\n\n\n\n
      4. Click Save<\/li>\n<\/ol>\n\n\n\n

        The final tag should look like this:<\/p>\n\n\n\n

        \"\"<\/figure>\n\n\n\n
        \n

        Be sure to publish the changes in your GTM container by clicking Submit and then Publish<\/p>\n<\/blockquote>\n\n\n\n

        The Conversion Linker Tag<\/h3>\n\n\n\n

        After saving the Google Ads tag, GTM will likely prompt you to add a Conversion Linker tag to your container. This is highly recommended to do, as it helps with aligning the first\/third-party context in which your various tags operate. This tag has no available configurations, so just save it and make sure its part of the published container.<\/p>\n\n\n\n

        Checking the implementation<\/h2>\n\n\n\n

        Once the tag has been installed you can verify that the data is flowing in correctly by using the Conversions reporting. While conversions you trigger manually for testing won’t count in your campaigns, you can still see that the conversion will become active.<\/p>\n\n\n\n

        \"\"
        On the far right-hand side you can see the conversion’s status.<\/figcaption><\/figure>\n\n\n\n
          \n
        1. Unverified – The conversion tag hasn’t been triggered yet<\/li>\n\n\n\n
        2. No Recent Conversions – Conversion tag triggered but no conversion was captured on a campaign over the past 7 days<\/li>\n\n\n\n
        3. Tag Inactive – Tag was previously active, but no conversions of any type were triggered over the past 7 days<\/li>\n\n\n\n
        4. Recording Conversions – Conversion tag active and conversion captured on a campaign over the past 7 days<\/li>\n\n\n\n
        5. Removed – Conversion tag has been disabled in Google Ads<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

          In this post I\u2019ll show how to quickly and efficiently set up a new pixel in Reddit.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,39],"tags":[],"_links":{"self":[{"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/posts\/5142"}],"collection":[{"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/comments?post=5142"}],"version-history":[{"count":9,"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/posts\/5142\/revisions"}],"predecessor-version":[{"id":5531,"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/posts\/5142\/revisions\/5531"}],"wp:attachment":[{"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/media?parent=5142"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/categories?post=5142"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/tags?post=5142"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}