Sync pixels
Direct sync
If you want to sync with us and we store the mapping table in our side, we should create a dedicated dsp ID for you and then you can use the following endpoint:
https://dx.bigsea.weborama.com/collect?dsp_id=<dsp_id>&eid=<your_cookieId>
Redirect sync
Redirect sync consists on synching with weborama and storing the mapping table in your side.
If you want to sync with .com cookie only, please use the following pixel:
If you want to synch with .com cookie and also set a .fr cookie, you should use the following pixel: https://dx.bigsea.weborama.com/collect?r=https%3A%2F%2Fyour_pixel%3Fpartner%3Dweborama%26id%3D%7BUUID%7D
Sync with the ecosystem
Our data providers
Our dataproviders are syncing with us and we store the mapping table in our side.
- Addthis: we sync our cookies with Addthis cookies in the following countries: US, UK, DE and FR.
- Sharethis: we sync our cookies with Sharethis cookies in the following countries: US, UK, DE, FR, IT, ES, RU, MX, AR
- 33accross: we sync with our cookies with 33accross in the following countries: US, RU, MX, AR
Our partners
- Liveramp: Liveramp is syncing its cookies with ours and store the mapping table.
Our clients
- Publicis: We are syncing with RUN (Publicis DSP/DMP) then RUN stores the mapping table.
DMPs
- WAM: we are synching by default our 3d Party data (BigSea) cookies with our DMP in all countries.
- Krux: We are synching our cookies with Krux and Krux stores the mapping table.