Documentation

# Third-Party Tracking

The documenation of implemented third-party marketing codes and nuances of integrations.

# Third Party Rule Naming Convention

{Third Party Tracker Name}: {What This Rule Does} Since there are titles the headline capitalization should be followed. All words should start with a capital letters, the only exception is articles and prepositions.

# Notes

Each new rule must contain a note. Author: Author Name or Initials
Company: Author Company
Dependencies: Rules that are dependent on this rule or that are required for this rule to execute. If unclear from description note on which pages the rule is expected to fire.

Examples:

  • Bing: Initialize Tracker Code
  • Bing: Track Page View
  • Bing: Track Transaction
  • Bing: Track Add to Cart
  • Decibel: Track Newsletter Sign Up
  • Decibel: Track Transaction

# Third-Party Code In Adobe Launch

  • Criteo (custom code), account id 33523
  • Decibel (Adobe integration code), account id da-13874, property id 253647
  • Donor points (custom code), account id hDYnR1co59yGfg
  • Facebook (custom code), account id 175734969458030
  • Floodlight (Adobe integration & custom code), account id 10657097
  • Fundraise Up (custom code)
  • Google Analytics Universal (custom code), account id for staging sites UA-85748307-1, for production site UA-85748307-2
  • iSpot (custom code), account id TC-4134-1
  • LeadRx (custom code), account id yqahgl42094
  • PlusMedia (custom code), account id for page views is 32293, for transactions 32293
  • Qualtrics test (custom code), account id ZN_bIsVs1xnVGENiVT
  • Rokt (custom code), account id 2799108467029446894_aac14a5747594e289c0f408d22988d02
  • SmarterHQ (custom code, not live yet), account id savethechildren
  • TheTradeDesk (custom code), account id a6t02yu
  • VDX (custom code), account id 791263
  • Wiland (custom code), account id 100229

# Third-Party Code In GTM

The information is incomplete as the code wasn't managed by DNL. Documentation includes only what we know and can see in GTM. Disabled/paused tags are not on the list.

  • 4Cite|Boomerang (custom code)
  • Amazon (custom code)
  • Bliss Media (custom code)
  • Cheetahmail (custom code)
  • Choozle (custom code)
  • Decibel (custom code), account id da-13874, property id 253647 duplicate, should it be disabled in GTM?
  • Google Ads (GTM integration code), multiple tags & conversion linker tag
  • Floodlight (GTM integration code):
    • Default tags use variable doubleclick-advertiser-id account id value is 5547516
    • SVTC tags use variable floodlight-account-id account id value is 8878870
    • GlassView tags use variable Glassview Advertiser ID account id value is 10359930
    • Media Storm tags use account id value 4853738
    • MNI tags use acccount id value 4319656
  • Microsoft Advertising, formerly Bing (GTM integration code)
  • Opt-In Monster (custom code)
  • Onclusive (custom code)
  • Outbrain (custom code)
  • RKD (custom code)
  • Smarter Remarketer (custom code)
  • Twitter (custom code)
  • Undertone (custom code)
  • Yahoo (custom code)

# Tracking Data

The following section applies to all code integration that accepts that data. The implementations are standardizes as much as possible.

# User Tracking

Analytics does not store any personally identifiable user data, so that information cannot be sent to the third-party tags. There are also many rules and regulations against storing or forwarding that data to third parties without user consent.

When the user is logged in their Luminate constituent id will be sent. If that's not availble their Adobe MCID will be sent to the tracker, so their browing behavior can be correlated in analytics.

# Product List Pages

In Adobe Analytics product list pages are not different from other page views. However, many third-party tracking codes view these pages differently. For those reasons, whenever we have product data, it is availabe in a page view event on product list pages. The product data can be sent along to the third-parties. The standarad page view in combination with the page type is used to identify these pages. Pages with product lists:

  • Gift catalog category pages
  • Sponsorship page with a list of children
  • Event ticket pages

# Product Pages

  • Donation form pages
  • Single gift catalog pages
  • Sponsorship child profile pages
  • TeamRaiser registration options pages
  • Event pages

# Product Ids

The sponsorship products will the child is instead of a standard id of the e-commerce product associated with sponsorship. This was done to ensure that the marketing attribution is more exact for various children profiles.

# Integration Code Notes

# Criteo

The Criteo tracker id is stored in the data element criteo:id to keep it dynamic.

Criteo tracker accepts two parameters ui_commerce & ui_sponsor to track gift catalog and sponsorship conversions. In Launch the value will be set accordingly on the product pages. On cart and thank you pages the values will be set based on the products in the user's cart. If the cart contains a sponsorship, then ui_sponsor will be set to 1. If the cart contains only gift catalog products, then ui_commerce will be set to 1. If the cart contains both products, both values will be set to 1.

Criteo Event Analytics Event Conditions
viewList pageView when list of products is shown
viewItem pageView when a single product is shown
viewBasket pageView when a cart page is viewed
viewHome pageView on gift catalog landing, faq, survey pages
trackTransaction transactionComplete always

# Decibel

The Decibel extension was used in Launch to add the Decibel tags to the site. The tracking id is entered inside the extension.

# Facebook

The Launch Facebook extension is very limited, it only allows to send events and provides no configuration for additional parameters. For these reasons it was not utilized. Instead, all Facebook code was entered into the rule.

The Facebook tracker id is stored in the data element facebook:id to keep it dynamic.

Facebook code tracks the following events:

Facebook Event Analytics Event Conditions
AddToCart transactionAddToCart always
Lead signUp always
Lead formSubmit if the form is on a survey page or has leadgen, enews, survey keywords in the name
PageView pageView always
Purchase transactionComplete always
ViewContent pageView on single product or product list pages

# Lead Tracking

The name of the page will be sent as content_ids parameter whenever the lead event is executed.

# Smarter Remarketer

Smarter Remarketer code tracks the following events:

Smarter Remarketer Event (Page Type) Analytics Event Conditions
onCrm if user Luminate cons_id or Adobe assigned mcid is present
onCartAdd transactionAddToCart always
onCartEmpty transactionRemoveFromCart always
onCartRemove transactionRemoveFromCart always
onCartView transactionRemoveFromCart always
onCheckout pageView if the user on the billing page (page with payment fields) of the transaction flow
pageView (category) pageView gift catalog homepage, gift catalog product pages, sponsorship list pages, event ticket pages
pageView (product) productView all product pages
pageView (purchase) transactionComplete transactionComplete

Smarter Remarketer requires price to best on product during add to cart event. Since it's not available in the data layer since it's not required by Adobe Analytics, 1 was set as a default value.

# Wiland

There was no available extension for Wildand, the code is inserted inside the rule. Wiland code will track either page view or transaction success event. The code has been configured to correctly record the needed event on transaction success pages.

If the user is logged in the user's Luminate constituent id will be sent to the tracker. Otherwise the Adobe's MCID will be set as a user's id to enable extended tracking of anonymous users.

# Third-Party Code Testing Instructions

Generic testing instructions for third-party tracking code testing. These steps can be executed on top of the testing instructions the vendor should provide.

# Testing Steps

  • Open up the page that user will be directed to by the vendor, include all the URL parameters that will be included on the final page
  • Verify that code is downloaded and data is being sent to the vendor via Network tab in web developer's tools; note the data on regular page views may or may not be sent, depending on the vendor scripts; contact the vendor for detailed testing instructions
  • Execute the expected interaction whether click or transaction, record the details of the interactions; for example transaction id, transaction amount, transaction time, or click time
  • Verify that code is downloaded and data is being sent to the vendor via Network tab in web developer's tools
  • Login to the third-party reporting tools and verify that your specific interaction from previous step shows up in the reports

# Developer Testing Instructions

These are the generic steps team DNL uses to test the code without having access or knowledge about how it operates. Any information deduces from the provided tracking code is used in validation.

  • Open up the web developer's toolbar
  • Load the page where the code should fire, depending on the vendor the page URL must contain URL parameters that the vendor will append
  • Check console to ensure you see no errors relating to the code
  • Open the network tab and see if the third-party request is being made
  • Ensure that the third-party code is loading
  • Verify that the data is being sent to the third-party on page load, this may or may not happen depends on the vendor and URL parameters specified and the configuration of the script
  • Run an expected interaction or interaction sequence with console open, keep track of the interaction details for data verification
  • Verify there are no obvious errors in the console
  • Verify that the data is being sent to the third-party server at the expected time
  • Check the URL of the data being sent to ensure that the expected tracked values are included

← Marketing code assignment →