You may need to set-up various 3rd party trackers in Slate. These trackers could include Google Analytics or advertising network conversion tracking from Google or Facebook.
You can setup these trackers directly in Slate, but the preferred method is to set-up a tag management system like Google Tag Manager (GTM). This allows you to centralize all your pixels for
easier visibility into all the tags placed on your websites
easily permission various agencies to place their own pixels
better control over page rendering times
Unless you have reasons otherwise, we suggest giving Waybetter full access to GTM and Analytics for the length of our engagement. This will allow us a full understanding of the potential impact of the changes we are making on your behalf. If you have a strong internal technical team with a good understanding of tag management best practices, ask them to assign the appropriate privileges to us for your deployment.
You can copy and paste the Google GTM code directly out of the GTM interface, but we suggest some slight additions.
Make sure you update the "GTM-CODE-HERE" text with id from the Google Tag Manager interface. Note: this is meant as guidance and should be customized to your instance and for exact code, please pull directly from your GTM instance.
var s_dl = {
"page_platform":"Slate"
}
var dataLayer = window.dataLayer = window.dataLayer || [];
dataLayer.push(s_dl);
(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src='https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);})(window,document,'script','dataLayer','GTM-CODE-HERE');
There are two methods you can use to set-up Google Tag Manager. Make sure you only use 1 method, otherwise loading Google Tag Manager twice will cause your website to load more slowly.
Directly in the Slate template
Within a configuration key
Alternately to setting GTM, you can directly setup global tracking tags from analytics and advertisers companies the same way.
"Once you have prepared the tracking code, you can embed this code into the /shared/build.xslt template file, which can be edited through the File Editor by clicking on the file name. You will want to place the code just above the </head> closing tag. This will ensure that the script loads at the beginning of the page load, which may be necessary for conversion events later. "
You will also need to wrap the example code in a <script> tag.
Benefits
Harder to change, less likely to accidentally break Google Tag Manager
Cons
Requires a technical resource to make this change
Alternately, paste the code into the "Embed Script on Slate Pages" configuration keys (Database > Configurations > Configuration Keys > Branding, Privacy, & Ping > Embed Script on Slate Pages)
Benefits
Easier to add and update
Cons
Anyone with configuration key access can easily change this code
If you embed multiple scripts on the page, its harder to manage them through this interface
Source: https://technolutions.zendesk.com/hc/en-us/articles/360033165651-Configuration-Keys
There are two methods of setting up conversion tracking:
Per-page tags
Site-wide tags
For each page you want to track, you set-up a separate and unique conversion pixel.
Pros
Limits the amount of data you send to advertising networks
Improves website page load speed, especially if you use multiple advertisers
Cons
More labor intensive for your tagging resource and potentially creating bottlenecks in workflows
Requires additional setup in GTM (or Slate) for every new page you want to track in the future
Makes consistent tag customization harder
For your entire website, you set-up a single conversion pixel that will fire on every page. Then the marketer or agency will use network's analytics tools to define the conversion event, usually a specific page URL.
Pros
All ad work can happen in the advertising network tools
No additional setup is required in GTM unless you bring on a new ad network
Data is consistent across all tags
This method is much easier for Slate direct installation
Cons
You send unnecessary data from pages that do not require tracking
Slows down page load for pages that do not require tracking
Increases the workload for marketers or the advertising agencies
To fully enable ad tracking in Slate from Google Ads, you need to manual tag your ads.
By default, Google Ads uses auto tagging and passes a "gclid" querystring to track ad data. On the backend, Google passes a more robust dataset of advertising data to Google Analytics, but reduces the amount of advertising information passed to 3rd parties like Slate. Slate is only able to determine the utm_source = Google and utm_medium = paid. utm_campaign, utm_content and utm_term are left blank.
If you use Google Analytics and Slate, you have two options:
Replace auto-tagging with manually UTM tagging: This is Google's preferred method.
Hybrid tagging: Leave auto-tagging on, manually add UTM tags and turn-off the UTM override in Google Analytics:
Select the Admin tag and navigate to the your school's property
Advanced Settings > Allow manual tagging (UTM values) to override auto-tagging (GCLID values) is unchecked
Save