What is the impact of Server-Side on consent?
These are two separate issues. Migrating to Server-Side does not in any way dispense with the collection of consent. This consent will be disseminated through the Server-Side, so that the partner data streams comply with the users’ indications.
Does a site that has already integrated a Client-Side TMS need to invest less to migrate to a Server-Side TMS?
Yes, to a certain extent, because a call is still required to activate the Server-Side. This call can be made from the Client-Side container, so you don’t have to implement it. A datalayer already in place will make this easier for you.
Does the Server-Side allow the use of other variables than those of the datalayer?
Yes, it does. The Server-Side allows you to interact with other applications in your martech stack to enrich the information – within the limits of the consents given by the users.
How soon will partner solutions be compatible with Server-Side?
It all depends on the nature of the actions performed by these partners: identify? collect? interact? For identification, you can do without the client-side tag; for collection, the switch seems possible; for interaction (e.g. personalisation), it looks more delicate. And it is very likely that for the same partner, some pages are tracked in Client-Side and others are processed in Server-Side. Note that Commanders Act already offers 30 ready-to-use Server-Side connectors.