With the proliferation of technical and legal initiatives aimed at limiting the levels of collection linked to cookies, such as the developments made by Apple ITP, it is becoming more complicated to perpetuate the installation of cookies by third-party services.
In order to guarantee the continuity of collection for the exclusive benefit of the advertiser using Eulerian solutions, we are offering a new cookieless configuration .
Purpose of cookieless collection
The purpose of cookieless collection is to:
Ensure collection in compliance with legal texts
Not to be dependent on the aberrant technical initiatives of certain publishers for their own profit
Guarantee a lasting link over time in the relationship between consumers and advertisers
No technical impact
Reuse of existing technical assets, such as your own customer identification system
How it works
Installing the Eulerian tag with the first party domain (classic installation Eulerian tags )
Configuring Eulerian to know which cookie to retrieve
No additional technical implementation is required to manage the configuration , we only need the Client to communicate to us the name of the cross-session cookie to use.
You will simply need to declare the key of this cookie in the Eulerian site settings:
Collection / Site Options
The cookie value provided must be a string that is unique to the individual and persistent cross-session.
The cookie must be deposited by the Client and readable by the Eulerian domain (therefore cookie deposited on the DOMAIN and not the host).
It is essential to contact your technical team to identify the correct cookie to use. This cookie must be:
1. a cross-session identifier
2. a lasting identifier over time
If you are using a platform like Shopfiy, Mirakl, PrestaShop, use the session identifiers provided.
Technical details:
Eulerian will read the cookie identifier declared by the Client, and will maintain a correspondence table between this identifier and the Eulerian cookie identifier (called ETUIX).
If the browser deletes the ETUIX cookie, we can find the server-side etuix cookie and perpetuate its session from the “MyVisitorId” cookie.
The Client is therefore the master of his data and his user identifiers.
You are now equipped to deal with future market developments and protect yourself from collection failures, such as Apple ITP!