TagCommander (deprecated)
Community home
  • Overview
  • Getting started
    • Setup Guides
      • AMP
      • Android
      • Angular
      • AngularJS
      • Consent Management
      • IOT & TV Apps
      • iOS
      • React Native
      • React
      • Serverside
      • VueJS
      • Websites
  • User manual
    • Getting Started
    • Data layer and data types
      • External variables
      • Internal variables
      • Event variables
      • Data storage
    • Container elements
      • Container
      • Tags
      • Events
      • Rules
        • Basic actions
        • Triggers
        • Perimeters & constraints
      • Advanced
    • Deduplication
      • Setup guide
      • Setup example
      • Deduplication reports
    • TagPerformance
      • Setup guide
      • Report analysis
      • Troubleshooting
    • Serverside
      • Datalayer
      • Container
      • Hybrid setup
      • Monitoring interface
      • Consents
    • Serverside v2
      • Facebook conversion API
        • Facebook CAPI through GTM
        • Facebook CAPI through web container
      • Events reference
    • Phoenix
    • APIs
  • Tips & tricks
    • Best Practices
      • FAQ
      • Common Container Strategies
      • Common Data Layer Properties
      • Common Trigger Strategies
      • Performance Optimization
      • tC.* attributes and methods
    • Widgets and extensions
      • Bookmarklet
      • Elements duplication
      • Chrome extension
      • Connected users visualization
Powered by GitBook
On this page
  • Ecommerce
  • Publisher

Was this helpful?

Export as PDF
  1. Tips & tricks
  2. Best Practices

Common Container Strategies

Container strategies for common setups.

A Container Strategy is the layout of the TagCommander Container of a site. Following you will find recommended Container Strategies for common types of websites and businesses.

Ecommerce

Ecommerce websites require a mix of personalization, analytics and conversion Tags. To optimise website performance it is recommended to use three Containers.

Container

Type

Placement

Tags

Head Container

<head>

All pages

A/B-testing and personalization

Body Container

<body>

All pages or catalog pages

Analytics and tracking

Funnel Container

<body>

Funnel pages

Conversion

With this setup it is possible to avoid conversion Tag JavaScript snippets on catalog pages—this results in smaller Container file sizes and therefore quicker loading times for SEO relevant catalog pages.

Publisher

Publisher websites primarily require analytics Tags. Therefore it is recommended to only use one Container.

Container

Type

Placement

Tags

Body Container

<body>

All pages or catalog pages

Analytics and tracking

Using one <body> Container helps to have minimal impact on the page loading time, which is crucial for SEO of Content pages like news articles. For AMP versions of the website it is possible to implement a Server-Side TagCommander.

In case A/B-testing and personalization Tags are used, the additional implementation of a <head> Container is recommended.

PreviousFAQNextCommon Data Layer Properties

Last updated 5 years ago

Was this helpful?