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
  • 1. Hybrid serverside : Managing consent client side with your CMP
  • 2. Managing consents with serverside's constraints
  1. User manual
  2. Serverside

Consents

Manage consents in Serverside context

PreviousMonitoring interfaceNextServerside v2

Last updated 4 years ago

1. Hybrid serverside : Managing consent client side with your CMP

If you setup a serverside tag from your web container, one way to manage consents is to fire or not your serverside tag depending of your CMP signal. Commanders Act offers with TrustCommander an integrated way to manage the firing of your tags depending of consent categories by a simple mapping beetween your tags and your categories.

Nevertheless, for a more precise management, even in hybrid setup we recommand to manage consent in serverside constraints.

2. Managing consents with serverside's constraints

We recommand to manage your serverside's tags through constraints, using a variable containing the list of optin categories.

    1. Create an consent_categories and feed it with the user's consent from your CMP. We recommand that consent_categories is feeded by a list of categorie's ids. (You can also create one variable per category of course if needed)

  • 2. Create a constraint in your serverside container that rely on consent_categories

  • 3. Attach the constraint to your tags

With TrustCommander, you can get your consent categories easily inside your client container using our Javascript APIcact('consent.get') and put the result inside a variable that will be send through your serverside tag. See documentation here :

https://community.commandersact.com/trustcommander/onsite-api/consent.get
external variable