Data Sources (Non-Data Layer)

Owned by Nathan Jackson
May 28, 2024
3 min read

 

Data sources that come from outside the data layer are collected in the Document -> Non Data Layer tab.

 

 

These sources include the following:

 

Data collection from a non-data layer source that occurs at the time of a Data Layer Event

These are other data sources that can be levered/accessed at the time a data layer event occurs. (e.g., query strings, window objects, etc.)

Other Data Sources Available at the Time of a Data Layer Event

Description

Query String

Query string parameters are parameters attached to the end of a url. They are extensions of the URL that help define specific content or actions being taken on the website/application. You can collect the values for a given parameter.

Window

The window object represents an open window in a browser. You can use the global window object to collect information about the current window that is open. Examples include:

  • window.location.href returns the href (URL) of the current page

  • window.location.pathname returns the path and filename of the current page

Static

A static data source is a persistent value that you would like to capture.

 

For example, if you wanted to ensure that you counted the number of times the Form Started data layer event occurred, this could be done with a static data source where the static value is "1". If you wanted to ensure that the product category variable was set to a static value of "product" anytime a Product Added to Cart event occurred, this could be done with a static value of "product".

Client Side Data Enrichment

These data sources rely on customization of tracking on the client side, meaning before an analytics tag is fired. Client Side data enrichment data sources rely on a technical resource to perform a manual implementation action to ensure data gets collected.

Client Side Data Enriched Data Sources

Description

Tag Manager Custom Code

This data source means that a technical resource needs to take a custom implementation action within the tag manager to support data collection. A primary example of tag manager custom code is DoPlugins() in the Adobe Launch Tag Manager.

Data integration

Data from this data source requires technical resources work with a third party vendor to implement tracking in the tag manager.

Server Side Data Enrichment

These data sources rely on customization of tracking on the server side, meaning after the analytics tag is fired (during or post processing). Sever Side data enrichment data sources rely on a technical resource to perform a manual implementation action to ensure data gets collected.

Sever Side Data Enriched Data Sources

Description

Data Import

Data from this data source is supported by the importing of data into the analytics platform.

Processing Rules

Data from data source is supported by a processing rule. For Adobe implementations, you can read more about Processing Rules and how to create them here.

Vista/DB Vista

This data source is available for Adobe implementations. Data from this data source requires a technical resource to apply a visitor segmentation rule or logic to your data after it is collected, but before it is stored. Read more here.

Data Integration

Data from this data source requires technical resources work with a third party vendor to implement data collection.