Server-Side
How long is the data kept?
Source (server-side data collection):
Live events inspector :
You can view up to 6 requests per minute for each type of event. And a bonus of 30 requests per hour for each type of event.
You can view the logs of your requests to the server-side for up to 7 days.
Destination (redistribution of data to your server-side partners) :
Event Inspector :
You can view up to 6 requests per minute for each type of event. And a bonus of 30 requests per hour for each type of event.
You can view the logs of your requests to your partners for up to 48 hours.
Event delivery:
The data storage time in the Event delivery report for your destinations is 30 days.
Health (monitoring dashboard for your server-side sources):
The data storage time in the Data quality report is 30 days.
What benefits can you expect from serverside?
Continuity in digital marketing
Web Performance
Data Quality & Monitoring
Enrichment
Security
Doesn't the sub-domain delegation mode present security problems?
There are several configurations and different sensitivities (CNAME, A-record, Reverse Proxy).
Using a WAF (Reverse Prox) is often used for security reasons and is one of the best ways of tracking your first-party events.
Is your CA ID similar to a First ID, for example?
The CAID operates in Silo mode. It is our customer's cookie on its perimeter, and can then be shared, but under the customer's control it is not a readable or shareable cookie.
What about support for certain consent mode features on the ss side?
Our platform includes a natively integrated consent solution that has been awarded the Consent Mode label by Google, so it all works well together.
What are your advantages over the other players in the market, i.e. Tealium / GTM server-side/GCP/Azure/etc.?
There are a number of differences with the players you mention. We are European, with hosting in France. The platform is highly valued by the business and is often more customisable.
Our Server Side solution can also be deployed in a GTM environment. Some of our current customers have switched their Server Side uses to us, even though their foundation was built on GTM for client side.
So the server-side solution does represent work for the devs in addition to the client-side aspect managed on the WA side?
This depends on whether you're looking at a full server-side or hybrid server-side context (some things managed on the client-side, others on the server-side).
Whatever the case, the server-side solution represents an enormous benefit, because once deployed you no longer need to worry about collection, but simply about activating your media partners.
What is the difference between hybrid and full server-side mode?
In hybrid mode, a tag needs to be deployed, your first-party needs to be set up and you're ready to go.
In full, an API to be activated within your environment, by your IT team.
Does the end of third-party cookies mean that CMPs will become obsolete and useless, or not?
No, because consent choices are stored in First-Party cookies, which can be made even more robust if you adopt certain first-party tracking optimisations.
Our CMP is ccompatible and certified by Google Consent Mode
Can this CAID be shared and used by OpenWeb purchasing platforms (Xandr, TTD, Adform etc) or only by Walled Gardens?
The main purpose of the CAID is to enable a site to recognise its visitors.
This identifier is the property of the site and is a tool serving the digital strategy of the customer and its partners. However, a hashed version of the CAID is sent to certain destinations
Is sub-domain delegation feasible for any type of cookie (e.g. Google Ads) and if so, can it be implemented on the TMS side rather than the dev side?
Client-side (saving cookies from client-side tags such as Google Ads) : Phoenix
Server-side: the CAID is used as the basis for the destinations, replacing the initial ids
Does the CAID have a configurable maximum retention period ?
The maximum duration of the CAID is 13 months. This duration can be configured in our interfaces.
What would be the financial impact of moving to Server-side (in terms of costs for the organisation)?
The financial impact depends on the volume of the site and/or apps. For all requests of this type, please do not hesitate to contact us directly to discuss them if you would like a personalised estimate.
You can also check the ROI of those who have already switched to server-side. Between 15% and +25 increase in conversion rates.
Can Commanders Act be used for remarketing / retargeting via server-side (on various zones: home page, products, categories, shopping basket, etc.)?
Yes, in the context of the end of cookies, we need to find exchange protocols that allow these digital mechanisms to continue.
With this in mind, the Server-side Commanders Act makes it easy to orchestrate the ingestion and redistribution of your data to your media partners.
We'll be sharing more personal data than before (capi / google enhanced conversion) - even if it's subject to cookies. Ultimately, for the user/internet surfer, accepting cookies means giving out much more information than before. What does the CNIL have to say about this?
Digital uses data to segment, target, measure and activate. Nothing has changed since then. You still have to comply with the RGPD.
The challenge is to find new components and methods on which to rely.
On the other hand, if data is exchanged in the future, the use of APIs will be much more secure than what was done with javascript. The advantage of an API for marketing is that you know who is sending, who is receiving and what is being received.
As WA teams are generally separate from dev teams, won't the Server Side aspect push implementation issues to the dev side where the trend was on the WA side with tag managers?
Dev teams are only called upon to work on a server-side implementation if you opt for a "server to server" approach. With the OneTag approach (used mainly by our customers), the opposite is true: you are much less dependent on your dev teams because serverside tagging opens up new no-code possibilities (enrichment, data cleansing, data quality, etc.) that were not possible with the client-side approach.
With the use of a server side - is it still possible to track "behavioural" data (Views, Clicks, Conversions) on specific elements (on consenting users)?
The same events will be collected in server side mode as in client side. It's just that instead of your analytics or other solution fetching the information from the browser (Adblocker, cookie limitation, etc.), it's pushed to it by Commanders Act in server side mode.
Is the CAID useful with media APIs (e.g. gec, capi)? Finally, is the CAID only useful if you use a data clean room?
As well as allowing you to exchange your identifiers with your media partners, the CAID will be of major interest in perpetuating your cookie on the server side and thus bypassing IT.
Do I need my IT to set it up?
No, there are self-hosted solutions.
We recommend using the Onetag in Tracking First for an initial implementation.
Tutorial OneTag :
First party Tracking :
Are all solutions available on serverside?
For the moment, not all solutions offer serverside tracking.
Most have it in their roadmap.
How do you validate the correct implementation of a serverside tag?
The recipe is just as important for serverside as it was for clientside.
With serverside, you can go even further by offering a complete range of incoming and outgoing hits.
The serverside enables the errors returned by partners to be tracked via dashboards.
Everything can be received by alert (slack, teams, mail, api etc...)
Last updated