Data element types for web extensions

In data collection tags, data elements are essentially aliases to pieces of data on a page. This data can be found in query string parameters, cookies, DOM elements, or other locations. A data element can be referenced by rules and acts as an abstraction for accessing these pieces of data.

Data element types are provided by extensions, and enable users to configure data elements to access pieces of data in a particular way. As an example, an extension could provide a “local storage item” data element type wherein the user could specify a local storage item name. When the data element is referenced by a rule, the extension would be able to look up the local storage item value by using the local storage item name that the user had provided when configuring the data element.

This document covers how to define data element types for a web extension in Adobe Experience Platform.

Data element types typically consist of the following:

Consider a situation where you want to allow users to retrieve a piece of data from a local storage item named productName. Your module may look like this:

module.exports = function(settings) {
  return localStorage.getItem('productName');
}

If you want to make the local storage item name configurable by the Adobe Experience Platform user, you can allow the user to input a name and then save the name to the settings object. The object might look something like this:

{
  itemName: "campaignId"
}

In order to operate on the user-defined local storage item name, your module would need to change to this:

module.exports = function(settings) {
  return localStorage.getItem(settings.itemName);
}

Default value support

Be aware that users have the option to configure a default value for any data element. If your data element library module returns a value of undefined or null, it will be automatically replaced by the default value the user has configured for the data element.

Contextual event data

If the data element is being retrieved as a result of a rule being triggered (for example, data elements are used in the conditions and actions of the rule), a second argument will be passed to your module which contains contextual information regarding the event that fired the rule. It may be beneficial in certain cases and can be accessed as follows:

module.exports = function(settings, event) {
  // event contains information regarding the event that fired the rule
};

The event object must contain the following properties:

The extension providing the event type that triggered the rule may optionally add any other useful information to this event object.