Domain Management

Domain management interface is key to configure well the data collect.
Commanders Act tracking can be improved by using a first party approach in addition to the third party one.
  • First-party cookies are stored by the domain (website) you are visiting directly. They allow website owners to collect analytics data, remember language settings, and perform other useful functions that help provide a good user experience.
  • Third-party cookies are created by domains other than the one you are visiting directly, hence the name third-party. They are used for cross-site tracking, retargeting and ad-serving.
Until now all the data collected on a website was done mainly by tags, 3rd party tags, because the data is pushed to external servers (not owned by the brand but by some partners).
Major browsers, such as Safari or Google Chrome, decided to not allow anymore 3rd party cookies. That means they will block cookies not coming from the brand itself but coming from partners (such as Commanders Act). They will detect all data flux pushed to a domain not related to the brand (3rd party domains).
As a result, the workaround to continue to track and push data from websites to partners, is to use a domain owned by the brand, a first party domain. And the cookies should be set by this domain, this is what is called ‘1st party cookie’ because it seems to be generated by the brand itself and not from partners.
There is a technical setup to do to initialize this 1st party tracking (on the domain level first and then on the cookie level).

What setup has to be done?

4 methods are possible:
  • A record (not the best solution anymore, but still usefull for Adblockers)
  • CNAME record (not the best solution anymore, but still usefull for Adblockers)
  • WAF proxy (easy to setup if you have a WAF like CloudFlare)
  • On-premise Proxy (more technical but prefered by some IT team)
Migration from 3rd party to 1st will be handled with Commanders Act consultants.