Features

Google

Feature	Description
Design : Data Sources	You can now leverage several new data source types: Tag Manager Custom Code - This data source type can be used when you plan on manually adding custom code to your tag manager to support tracking. Apollo will not perform any configurations in the tag manager for this data source type. Data Import - This data source type can be used when you plan to import data into your analytics platform to support tracking. Apollo will not perform any configurations in the tag manager for this data source type. Data integration - This data source type can be used when you plan to leverage a 3rd party integration within the tag manager or analytics platform to support tracking. Apollo will not perform any configurations in the tag manager for this data source type.
Design : Assign Reporting	You can now expand the details for any Variable and mark it as a Global Variable. Marking a Variable as a Global Variable will require that you choose the Data Source you want to pulling data from for the global setting. Deployment to tag manager for Global Variables will result in the Variable being set in every analytics tag as long as the data source was populated with a value during the visit prior. A good use case for this feature is the ability to capture values for the detailed_event parameter for every event in reporting.

Adobe

Feature

Description

Deploy: Builds [Tag Manager]

Apollo will not overwrite any manual changes you make to the optional AEP settings on Send Beacon rule actions provided by the AA via AEP Web SDK extension.

Additionally, Apollo will provide the following default values when creating a rule:

Type: ""
Additional XDM Data : ""
Data : ""
Merge ID : ""
Dataset ID : ""
Document Will Unload : False
Render Visual Personalization decisions : False
Decision Scopes: Manually enter scopes
1. Scope : ""

Bug Fixes

Adobe

Feature	Description
Design : Edit Variables	Resolved an issue within the expiration setting for eVars, where the Cart Add event was spelled incorrectly in the UI (was not deployment impacting).