After you configure the Adobe Experience Platform Web SDK tag extension, you must configure your action types.
This page describes the action types supported by the Adobe Experience Platform Web SDK tag extension.
Sends an event to Adobe Experience Platform so that Adobe Experience Platform can collect the data you send and act on that information. Select an instance (if you have more than one). Any data that you want to send can be sent in the XDM Data field. Use a JSON object that conforms to the structure of your XDM schema. This object can either be created on your page or through a Custom Code Data Element.
There are a few other fields in the Send Event action type that could also be useful depending on your implementation. Please note that these fields are all optional.
After you have received consent from your user, this consent must be communicated to the Adobe Experience Platform Web SDK by using the “Set Consent” action type. Currently, two types of standards are supported: “Adobe” and “IAB TCF.” See Supporting Customer Consent Preferences. When using Adobe version 2.0, only a data element value is supported. You will need to create a data element that resolves to the consent object.
In this action, you are also provided with an optional field to include an Identity Map so that identities can be synced once consent is received. Syncing is useful when the consent is configured as “Pending” or “Out” because the consent call is likely the first call to fire.
Use this action to modify an XDM object as a result of an event. This action is intended to build up an object that can later be referenced from a Send event action, to record the event XDM object.
In order to use this action type you must have defined a variable data element. Once you choose a variable data element to modify, an editor appears, similar to the editor for the XDM object data element.
The XDM schema that is used for the editor is the schema that is selected on the variable data element. You can set one or more properties of the object by clicking on one of the properties in the tree on the left, and then modifying the value on the right.For example, in the screenshot below, the producedBy property is getting set to the data element “Produced by data element.”
There are some differences between the editor in the update variable action versus the editor in the XDM object data element. First, the update variable action has a root level item labeled “xdm.” If you click on this item, you can specify a data element to use to set the entire object. Second, the update variable action has checkboxes to clear the data from the xdm object. Click on one of the properties on the left, and then check the checkbox on the right to clear the value. This will clear out the current value before setting any values on the variable.
After reading this article, you should have a better understanding of how to configure your actions. Next, read about how to configure your data element types.