Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

https://www.youtube.com/embed/QEUmCLb490E?rel=0

Selecting the Tag Manager box within the Builds module will deploy everything needed by the tag management system. This includes data layer elements, tag extensions and tag management rules. Since all information about the implementation is stored in Apollo’s database, it can be programmatically sent from Apollo to the tag management system via an API connection.


To show how Apollo deploys to the tag management systems, let’s go through some examples.


Use Case 1 : Apollo creates a new property upon initial deployment

In this example, an API connection has been made between Apollo and a tag management system. Once the Tag Manager deployment has occurred you can navigate to the tag management system and view the results.


Within the tag management system, you will see a date/time stamped configuration that matches the name of the Apollo property used to generate it and the original creation date/time.


Below is an example of a Tag Manager property created in Adobe Launch:



This tag management system configuration contains the same information that was configured in the Design and Document modules of Apollo. For example, in the case of a Google Tag Manager deployment, that means you will see all Google Analytics tags, variables, triggers, and templates required for analytics tags configured.


Below is an example showing all Rules configured in Adobe Launch.



If you inspect any of the items within the tag management system, you will see that they each leverage the data layer names from the Documentation module and that data is mapped to the specific analytics tool variable numbers specified in the Apollo Assign Custom Variables module.


Below is an example from Adobe Launch:



At this point, the tag management system can be used as it has been traditionally. Various elements of the implementation can be moved from development to production until all elements are deployed.


Use Case 2 : Apollo deploys to a pre-existing tag manager property

In this example, an API connection has been made between Apollo and a tag management system. Additionally, a pre-existing tag manager property ID has been associated the Apollo property. Once the Tag Manager deployment has occurred you can navigate to the tag management system and view the results.


Within the tag management system, the Tag Manager Property will have remained the same as it was. If you inspect the property, you will see new components Apollo has added to the property.

  • No labels