Commanders Act

What Is Commanders Act?

In 2010, online advertising in France faced a problem that would only get worse: marketers needed to deploy dozens of tracking scripts — ad pixels, analytics tags, heat-mapping tools — to every page of their websites, each one added individually by developers, each one a source of page load delays and privacy exposure. A Paris-based company called TagCommander launched that year with a specific answer: centralise all marketing tags in one container, load them once, fire them conditionally based on user consent and page context.

The company spent the next decade becoming the dominant European alternative to Google Tag Manager. In 2019 it rebranded to Commanders Act, signalling a broader ambition: not just tag management, but a full customer data platform layered on top of the tag infrastructure it had already built. Gartner and Forrester recognised the result — Commanders Act is the only French CDP listed by both analyst houses, a distinction it uses heavily in enterprise sales conversations.

The product has since evolved further. The third-party cookie collapse forced a rethinking of how data flows from browsers to ad platforms. Commanders Act built a server-side collection architecture in response: instead of running Meta pixels and Google tags in the visitor's browser, those events are collected server-side and forwarded to ad platforms via Conversions APIs. Page load times improve, ad blocker interference drops, and no third-party script has direct access to the visitor's browser.

This is the version of Commanders Act that exists in 2026: an enterprise platform combining tag management, server-side event collection, consent management, first-party CDP, and audience activation, all hosted in France.

Key Features

Server-Side Tag Management

Traditional client-side tag management (including Google Tag Manager's standard mode) loads JavaScript in the visitor's browser. Each tag — a Meta pixel, a Google Analytics snippet, a heat-mapping SDK — executes directly, can read browser storage, and communicates independently with its destination server. Ad blockers target these scripts; GDPR data flows become difficult to audit.

Commanders Act's server-side approach moves the collection point upstream. The website sends a structured event to a server controlled by the customer (or hosted by Commanders Act in France). That server then forwards only approved, transformed data to each destination. A Meta pixel event reaches Meta CAPI; a Google Analytics event reaches GA4 via the Measurement Protocol. No third-party script runs in the browser.

The performance impact is measurable. Reducing client-side script execution typically improves Core Web Vitals scores by 15-40%, depending on how many tags are migrated server-side. For large e-commerce sites where conversion rates are sensitive to load times, this is a meaningful secondary benefit of a compliance-driven architecture.

Customer Data Platform

The CDP layer ingests events from the tag management system and from CRM, offline, and API sources to build unified customer profiles. Commanders Act stitches together anonymous sessions, authenticated user identifiers, and offline purchase records into a single profile per customer. The resolution logic handles cross-device and cross-channel journeys.

Audience segments can be built on any combination of behavioural, demographic, and transactional attributes. Once built, audiences sync in real-time to connected destinations — Google Ads Customer Match, Meta Custom Audiences, Salesforce, or proprietary data warehouses. The real-time sync removes the batch delay common in older DMP architectures; a customer who converts in-store can be suppressed from paid acquisition campaigns within minutes.

100+ Server-Side Connectors

Commanders Act maintains a library of over 100 server-side destination connectors, updated monthly. The critical integrations for European enterprise use — Meta CAPI, Google Ads Enhanced Conversions, Amazon Ads, TikTok Events API, LinkedIn CAPI, Snapchat CAPI — are maintained with current API versions. New platform API changes (like Meta's periodic CAPI versioning) are absorbed by Commanders Act engineers rather than by the customer's development team.

Building a custom connector requires API knowledge but uses a structured template system. Teams with internal engineering resources can develop proprietary connectors for internal data destinations.

Consent Management and IAB TCF 2.2

Commanders Act includes a consent management platform that integrates natively with its tag management layer. Consent signals from the CMP directly govern which tags fire and which server-side events are forwarded. IAB TCF 2.2 purposes map to specific data flows, making it possible to demonstrate — through a documented audit trail — that data collection respects each user's consent choices.

This native integration avoids the workaround most Google Tag Manager users rely on: a third-party CMP that injects consent variables into the dataLayer, which GTM then checks inconsistently. The Commanders Act stack treats consent as a first-class data type throughout the collection pipeline.

ePrivacy EU Certification

Commanders Act received ePrivacy EU certification in 2017, making it one of the first tag management platforms to hold the certification. The ePrivacy seal validates that the platform processes personal data in accordance with EU data protection law. For enterprise customers whose DPOs require documented evidence of vendor compliance, this is a usable third-party attestation — not just a self-reported claim.

Pricing

Commanders Act is an enterprise product with custom pricing. There is no self-service trial, no published rate card, and no free tier.

Pricing is based on event volume, number of connectors, CDP usage, and support tier requirements. Deals typically range from mid-five figures to mid-six figures annually for large deployments. The lack of transparent pricing is a genuine friction point for organisations evaluating the platform without an existing vendor relationship.

The evaluation process follows a standard enterprise SaaS pattern: a demo with a solutions engineer, followed by a scoped proof of concept, followed by a commercial negotiation. For organisations that have already determined they need server-side tag management with European data residency, this process is manageable. For organisations still evaluating whether server-side tagging is necessary, the absence of a trial tier slows the evaluation considerably.

The case for cost justification typically centres on three measurable outcomes: improved ad conversion tracking through Conversions API (recapturing data lost to ad blockers and iOS privacy changes), reduced page load times through fewer client-side scripts, and simplified GDPR compliance documentation through centralised data governance.

EU Compliance and Privacy

All Commanders Act customer data is processed and stored in France. The company is a French SAS, fully subject to GDPR and CNIL supervision. French data protection law requires CNIL-aligned practices; Commanders Act positions this as a guarantee rather than a differentiator, since the legal obligation leaves no room for flexibility.

The ePrivacy EU certification provides third-party validation. The IAB TCF 2.2 integration supports documented consent management. The server-side architecture means customer DPOs can demonstrate that no third-party marketing vendor has direct browser access to visitor data — a significant simplification of data flow documentation compared to client-side tag stacks.

For organisations subject to the NIS2 Directive (network and information security) or the French RGPD interpretations issued by CNIL, the EU data residency and French jurisdiction are directly relevant to compliance documentation requirements.

Who It's Best For

Enterprise e-commerce and retail groups with large paid acquisition budgets benefit most. Server-side Conversions API integration with Meta and Google directly addresses the signal loss from iOS App Tracking Transparency changes, which continues to reduce reported ROAS for client-side pixel implementations. Companies spending over €500k/year in paid social typically recover measurable attribution improvement.

Financial services and insurance organisations subject to strict data governance requirements will find the French data residency, ePrivacy certification, and IAB TCF 2.2 compliance easier to document than a US-hosted tag management solution.

Media groups and publishers running complex audience monetisation strategies, with multiple ad tech partners requiring data syndication, benefit from the real-time CDP audience activation and the breadth of server-side connectors.

Commanders Act is a poor fit for small and mid-market companies. The enterprise sales process, minimum contract size, and implementation complexity require dedicated internal resource or agency partnership. Organisations with fewer than 1 million monthly sessions and limited internal data engineering capacity should evaluate Matomo Tag Manager, Stape, or JENTIS instead.

The Verdict

Commanders Act occupies a specific position in the European martech market: the only French CDP with Gartner and Forrester recognition, a server-side-first architecture built before the third-party cookie collapse made server-side tagging mainstream, and a compliance posture — French data hosting, ePrivacy EU certification, IAB TCF 2.2 — that is genuinely differentiated from US alternatives.

The tradeoffs are real. There is no self-service entry point. Implementation requires expertise. The integration marketplace, while growing, remains smaller than Google Tag Manager's community library. For a large European enterprise that has already decided it needs GDPR-compliant server-side tag management with a CDP layer, these tradeoffs are acceptable. For a company still deciding whether server-side tagging justifies the investment, the absence of a trial tier makes evaluation genuinely difficult.

FAQ

How does Commanders Act differ from Google Tag Manager? Google Tag Manager is a free client-side tag manager that runs scripts in the visitor's browser and sends data to Google's US infrastructure. Commanders Act offers server-side tag management where data collection happens on servers hosted in France, eliminating client-side privacy risks and keeping data within EU jurisdiction. GTM has a far larger free template library; Commanders Act wins on compliance architecture and first-party data control.

Is Commanders Act GDPR compliant? Yes. All customer data is processed and stored in France. The platform holds ePrivacy EU certification, is IAB TCF 2.2 compliant, and follows CNIL guidelines. The server-side architecture means ad platforms receive only data the customer explicitly chooses to share.

What is server-side tagging and why does it matter? Traditional tag managers load third-party scripts in the visitor's browser, which slows pages, leaks data to vendors, and is blocked by ad blockers. Server-side tagging moves event collection to a server: your site sends events to your server, which forwards only approved data to ad platforms. Page loads improve, data leakage reduces, and ad blocker interference drops.

What is the difference between Commanders Act's tag management and its CDP? The tag management system (inherited from TagCommander) collects and routes events. The CDP layer, added later, stitches events into unified customer profiles and activates audiences to ad platforms and CRMs. Both modules are available within a single platform.

Does Commanders Act offer a free trial? No. Commanders Act sells through direct enterprise sales with custom pricing. There is no self-service trial, free tier, or published rate card. Evaluations begin with a demo and typically progress through a proof-of-concept engagement.