Enabling first-party cookies in your tracking script allows you to track your users more accurately. When first-party cookies are enabled, cookies are created on your website instead of Sendinblue or a third party.
How does it work?
Enabling first-party cookies adds the parameter “_se” to the URLs redirecting to your website. In rare cases, this may cause issues with loading a page on your website if the application or web server doesn’t handle unknown parameters.
How to resolve potential issues?
Review the options below to resolve common issues that occur when implementing first-party cookies on your website.
Page Not Found
If your page doesn’t show when the URL is clicked, you may need to confirm how your web server checks parameters.
- If your web server expects a known set of parameters, add “_se” as a parameter.
- If your web server evaluates query parameters to locate a resource, the server should skip evaluating “_se”. Configure your server settings to allow “_se”.
URL missing _se parameter
Your application clears the URL
An application can be configured to read query parameters to determine states in a single-page or multi-page experience. It can clean its own URL to correctly represent the state it is in.
- Your website framework should add “_se” as an exception and/or skip taking any action on it. Make sure the parameter persists in the URL until the tracking script has done its job.
- If your website clears and cleans unknown values from the address bar, make sure the Sendinblue tracking script calls happens as early as possible, ideally before loading any library. To help the tracking script calls to happen quickly, we advise you to place the Sendinblue tracking script as high in the website header as possible.