When Adobe Tag's debug mode is enabled by running _satellite.setDebug(true) in your browser console, the logs may show additional errors. This page covers the error codes that may show and how to rectify the errors.
ACRGTAG-100 - Cannot load gtag library
The extension was unable to load the main gtag library, typically found at https://www.googletagmanager.com/gtag/js?id=[ACCOUNT ID]. This is typically caused by an ad blocker in your browser blocking the JS library from loading, but it could also be caused by other network errors.
Open your developer tools' network tab to see what response code the library is loading.
ACRGTAG-101 - Custom config code error
The extension caught an error in either the Pre-Account Initialization Code or the Post-Account Initialization Code .
Review the custom code blocks and rectify any JavaScript errors.
No accounts were added or configured, and thus there was nothing to load.
Add an account to start sending data.
ACRGTAG-103 - Library already loaded
The main gtag library has already been loaded on the page. If you are using the "Preload the gtag.js library" action, you may be calling this multiple times.
If you are preloading the library, you can remove this action. Otherwise, no further changes are required.
The data layer is not an array and data cannot be pushed to it.
You may be using the name "dataLayer" for another tool. If so, you should rename the data layer variable name to something else. Acronym recommends using gtagDataLayer as an easy replacement. The current value of the data layer variable is passed alongside the error message for easier debugging.
ACRGTAG-201 - No accounts enabled
No accounts were enabled when this rule action ran. This could happen when you are using data elements to set the enabled/disabled status for an account and they all return false, or if you have not enabled any accounts.
Enable an account to send data to that account. Otherwise, if no accounts are enabled, verify if you still need this rule action.
ACRGTAG-202 - An account was removed in the extension config
This happens when an account was removed in the extension configuration, but still exists in the rule action settings. Due to the limited nature of what extensions can see and do, we cannot automatically update rule actions when an account is removed in the extension configuration.
Re-save the rule action to remove the account from the rule action settings.
