FCI Release Notes for Digital Source Tracker Mar 2022

Release Schedule

Release At-a-Glance

New Features

Bing Integration

What:

With Integration to Bing Ad Networks, digital marketers can now report on their Digital Ad Costs for Bing Ads alongside those of Google Ads in order to get a richer perspective and view of their Digital Ad spending across both Ad Platforms, and how those ads and costs contribute to digital responses and revenue.

Where:

The following fields have been added or modified in the Aggregate Database Entry object to account for Bing Spend Data.

Who:

Digital Marketers that are reporting and doing analysis on costs associated to digital ad campaigns that include Bing ads, and how that correlates to digital responses and Revenue.

Why:

Previously, the only cost data available in Digital Source Tracker was for Google Ads. Customers with Bing Ads weren't able to include the cost analysis for those ads in their reporting and dashboard components that tracked items like Cost Per Lead, Cost Per MQL, etc.

When:

Once your Bing Integration is setup, the Bing Spend data will flow into the new fields and will be available for reporting. See below for how to setup the integration and for how to modify the existing Dashboards and Reports (for existing customers) so the data is properly reflected in those components.

How:

In order to fully take advantage of the Bing Ad Network Integration feature you need to:

• Setup the Bing Integration.
• Update Reports and Dashboards (for existing Digital Source Tracker Customers that launched before Feb 2022)

Key considerations

• Bing spend data will only populate if you have successfully completed the Bing Integration. (see above)
• Any existing Dashboards and Reports will not automatically reflect Bing Spend data. See above for instructions on how to incorporate.

Improvements

Cookie Consent Form Support

What:

With support for Cookie Consent Forms, Digital Source Tracker can now respect user decisions on whether or not they consent to cookie tracking based on how they submit the form.

Where and How:

To enable this, a web developer will need to add a small bit of code that will execute after a visitor has clicked to opt out of cookie tracking, and similarly add a small bit of code that will execute after a visitor has clicked to opt in to cookie tracking. Here are the code snippets they'll need:

// use this code snippet when a visitor has chosen to opt out of tracking - and their choice only affects the current page
fcdsc.trackingOptOut();

// use this code snippet when a visitor has chosen to opt out of tracking - and their choice should persist across the session
// this creates a session cookie that notifies DST to not track the visitor during this session
fcdsc.trackingOptOut(true);

// use this code snippet when a visitor has chosen to opt in to tracking
fcdsc.trackingOptIn();

Who:

Customers that have Cookie Consent Forms on their webpages

Why:

In order to be GDPR compliant, many customers are adding Cookie Consent Forms to their webpages to get user consent on being tracked with Cookie Data. Since Digital Source Tracker is tracking user activity, this new capability allows Digital Source Tracker to be in compliance with the user's cookie preferences on the site.

When:

Once the code snippets are added to the Cookie Consent form pages, Digital Source Tracker will begin respecting user decisions related to the Cookie Consent Form.

Change to Referral UTM Setting

What:

Digital Referral touchpoints that do not have any UTM parameters set in the URL will now be set as follows:

• UTM Medium = "Referral"
• UTM Source = <Referring page>

Previously UTM Source was set to "Referral" and UTM Medium was blank

Why and Where:

This change makes Digital Source Tracker referral data aligned with how Google Analytics sets referrals in the utm medium parameter. This allows for the correlation of Google Analytics pageviews from referrals to Digital Touches that turn into MQLs or Revenue from Digital Referrals, as in the example component below from the Digital Effectiveness Dashboard. Before, this data would not be able to be correlated as "referral" being set in utm source.

When:

This change will be automatically made for new referral touchpoints. However, for existing data, you should Contact Support if you wish to back populate the utm settings for referral touchpoints.

Key considerations

• If you are using any existing reports that involve digital referral data in the grouping or filtering as utm source = "referral", that report will be impacted going forward
• To align any existing data with referrals with new data going forward, you may consider backpopulating the data. To do this, Contact Support for assistance.