Publisher Demand connection
- Connecting Native (fluid) ads to Browsi engine
- Header Bidding support (Body Bidding)
- Header Bidding Demand Integration – Prebid.js
- Appnexus Demand Integration
- Collegare la tua richiesta DFP (Italiano)
- Conectando su demanda DFP (Spanish)
- Connectez votre demande DFP (French)
- DFP demand integration
- AdForm Demand Integration
Cookie usage with Browsi
Which cookies does Browsi use?
Browsi uses two different cookies dropped on the publisher site. These two cookies are considered to be first party cookies, meaning they live on the publisher domain and are not shared or synced with other domains. The 2 cookies are persistent cookies which hold a set expiration date.
- Browsi Session Cookie
Used to gather the data around the user session on the publisher’s site and, by default, expires after 30 minutes of inactivity by the user (most common definition of session by Google analytics https://support.google.com/analytics/answer/2731565?hl=en).
- Browsi User ID Cookie
Browsi marks users by using a specific user key that is generated per user, that key is created upon user’s first encounter with Browsi on a specific domain (no cross domain). That key is stored in a cookie, with 1 year expiration date.