AudienceView Documentation

• Google Tag Manager (GTM) Content Map
• The Basics of Google Tag Manager
• The Benefits of Google Tag Manager
• The Risks of Google Tag Manager
• Key Concepts of Google Tag Manager
• Getting Started with Google Tag Manager
• Enabling Google Tag Manager in AudienceView
  • Enabling Google Tag Manager in Application Security
  • Enabling Google Tag Manager on Your AudienceView Site(s)
  • Testing the Google Tag Manager Installation
• Before We Go Any Further – We Need to Talk About the dataLayer
• Just One More Thing About Variables
• Google Tag Manager Use Cases
  • Use Case One (GTM) - Implementing Google Analytics through Google Tag Manager
  • Use Case Two (GTM) – Implementing a Basic Conversion Tag
  • Use Case Three (GTM) – Sending Errors as Google Analytics Events
  • Use Case Four (GTM) - Implementing Conversion Tags for Specific Products
  • Use Case Five (GTM) – Pushing Customer Search Input into Google Analytics
  • Use Case Six (GTM) – Implementing Sub-Domain Tracking with Google Analytics
• Google Tag Manager - Tools and Troubleshooting
• Technical Appendix - Google Tag Manager
  • av.cart
    • av.cart - Order Products
    • av.cart - Dictionary objects
    • av.cart - Dictionary Lookup Functions
    • av.cart - Utility Functions
  • av.order
    • av.order - Order Products
    • av.order - Dictionary Objects
    • av.order - Dictionary Lookup Functions
    • av.order - Utility Functions
  • av.page
  • av.session
  • transaction
  • dataLayer Events

Product Guides > 6.8.0 Product Documentation > 6.8.0 Application Documentation > AudienceView Configuration Guides > Google Tag Manager Configuration Guide > Google Tag Manager Use Cases > Use Case Six (GTM) – Implementing Sub-Domain Tracking with Google Analytics

---

Table of Contents | Previous

---

Sometimes your online presence can be spread over multiple websites. A fairly common scenario is to have a website that provides customers with information about upcoming events and your business located on the main domain of your business (e.g. www.audienceview.com). The 'Buy' buttons on this website link to the AudienceView ecommerce platform, in this case a sub-domain of your main domain (e.g. tickets.audienceview.com). Your analytics strategy might be to consider that a visit from website to the other is considered a single visit. With this strategy you can begin to track the behavioural flow between both websites in Google Analytics. You can also ensure that the original source of the transaction is maintained and is not lost when the customer clicks through from your main domain to the sub-domain after having followed some advertising or marketing communication to land on the main domain.

Implemention

The video below demonstrates the steps required to complete this use case. Please watch the video in conjunction with the documentation.



This use case covers implementing sub-domain tracking with Classic Google Analytics. We will cover implementing sub-domain tracking with Universal Analytics in a later use case. This use case assumes that Google Tag Manager is deployed on both your sub-domain (AudienceView) and your main domain. Once you have Google Tag Manager deployed on both domains the configuration is quite simple and can be incorporated into your normal Google Analytics pageview tags. It is a good practice to fire your main domain tags within their own container to keep the configuration clean.

Pageview Tag Configuration

Within your Google Analytics pageview tags there are just two extra pieces of configuration required. This configuration should be identical on the main domain and sub-domain tag configuration.

1. Under More Settings -> Domains and Directories: Check the box next to 'Domain Name' and input the name of your main domain (e.g. audienceview.com).
2. Under More Settings -> Search Engines and Referrers: Check the box next to 'Referrers to Ignore' and enter your main domain into the list box (e.g. audienceview.com and www.audienceview.com). This configuration will stop identifying the main domain as the referrer when users click-through from the main domain to the sub-domain.

Summary

We modified our pageview tags so that Google Analytics will treat a visit between the main domain and sub-domain as a single visit and not lose any of the source information of the original visit to the main domain. The source information will be present on the whole session which means that it is possible to report on the original source of a conversion in AudienceView when the source first directed to the main domain and the customer followed a buy link to the sub-domain.