Loading...

Removing WebTag 2.0

This page provides detailed instructions to remove Acquia CDP WebTag from your website, both for manual and Google Tag Manager (GTM) implementations.

Remove the manually implemented WebTag 2.0

Use the following checklist to remove manually implemented WebTag 2.0:

S.No.TaskDescription
1Remove Global WebTag 2.0 script

Delete the following from your <header> tags:

  • The $A1Config configuration block
  • The script source reference (acquia-cdp-webtag.js or a1.js)

2Remove Customer Object configurationRemove all visitor object configurations and customer tracking code.
3Remove tracking events

Remove all event tracking code snippets as applicable:

  • Login/logout tracking code
  • Product browsing events
  • Category browsing events
  • Cart update events
  • Checkout events
  • Onsite search events
  • Any custom event tracking code

Example of code to remove

// Remove this configuration block
var $A1Config = {
    webtagId: "your-webtag-id",
    tenantId: xxx,
    host: "//url.endpoint.com"
};

// Remove this script reference
<script src="https://scripts.agilone.com/latest/acquia-cdp-webtag.js"></script>

Remove the Google Tag Manager (GTM) implemented WebTag 2.0

Use the following checklist to remove WebTag 2.0 implemented through GTM:

S.No.TaskDescription
1Access GTM workspaceLog in to Google Tag Manager and access the account and workspace for your website.
2Remove essential tags

Locate and remove:

  • CDP - Global tag
  • CDP - Customer Object tag
3Remove optional tags

Remove all CDP event tags as applicable:

  • CDP - Login
  • CDP - Logout
  • CDP - Products Browsed (PDP)
  • CDP - Cart Updated
  • CDP - Category Browsed (PLP)
  • CDP - Search
  • CDP - Checkout
  • Any custom CDP tags
4Publish changesPublish your GTM container after you remove all CDP-related tags as applicable.

Verifying the removal of WebTag 2.0

After removing the WebTag, verify using the following steps:

  1. Open your website in Chrome
  2. Press the F12 key to access Chrome Developer Tools.
  3. Check the Network tab.
  4. Verify that no calls are being made to:
    • scripts.agilone.com
    • Acquia CDP endpoints
  5. Reload the page and perform basic interactions to confirm that no CDP-related scripts load.

If you continue to see CDP-related network calls, review your implementation and ensure all components have been removed.

Did not find what you were looking for?

If this content did not answer your questions, try searching or contacting our support team for further assistance.

Back to Section navigation