/
Making Manual Updates to Apollo Managed Tag Manager Components

Making Manual Updates to Apollo Managed Tag Manager Components

Owned by Nathan Jackson
Last updated: May 28, 2024

With Apollo implementations, Tag Manager components/configurations fall into one of two categories:

  1. The components Apollo doesn't know about

  2. The components Apollo does knows about

Apollo handles components in these categories differently. We go into detail about how Apollo handles manual tag manager updates to the components in each categories below

 

Scenario 1: You made a manual change to a component Apollo doesn't know about

The components Apollo "doesn't know of" consist of any components/configurations Apollo did not create/make. These include:

  • Data elements you manually create

  • Rules you manually create

  • New rule triggers/events you manually add (regardless of whether or not Apollo created the rule originally)

  • New rule conditions you manually add (regardless of whether or not Apollo created the rule originally)

  • New rule actions you manually add (regardless of whether or not Apollo created the rule originally)

  • Extensions you manually add that aren't included in the list of extensions Apollo configures

  • New Environments you manually add

All of these changes are things Apollo will not overwrite with subsequent deployments. Apollo is intentionally designed this way to allow you to add non-analytics tagging and configurations to your tag manager property

 

Scenario 2: You made a manual change to a component Apollo does know about

The components Apollo "knows of" consist of the components it configures during deployment. These include:

  • Analytics data elements

  • Analytics rules

  • Analytics events/triggers

  • Analytics rule conditions

  • Analytics rule actions

  • Analytics extensions

Apollo will overwrite changes to the above components on subsequent builds. This includes if you change the names or configurations of these components. The nuanced exception being analytics extensions. Before you make any changes to extension configurations, it is recommended that you review which extension configurations Apollo will and will not overwrite in the articles linked below:

  • AA Product String Builder

  • Adobe Analytics

  • Airbrake JS Notifier

  • Apollo QAX

  • Core

  • Data Layer Manager

  • Experience Cloud ID Service

Two types of manual updates to Apollo-managed components may cause future deployments to the tag manager to fail. Please follow the guidance below:

  1. Never manually delete a component that Apollo configures. If a component is no longer needed, you should make the appropriate update in Apollo and Apollo will remove the component on a subsequent deployment to the tag manager.

  2. If you choose to make a copy of a component that Apollo manages, it is recommended that you ensure the copy has a different name than the original.

Additional Notes

If you are having trouble identifying which components Apollo does and does not manage, we recommend implementing the Organization Marker feature, which appends Apollo managed component names with a common suffix/prefix. By default, Markers are not added to data elements.