Viewability Predictor Integration
Viewability Server Integration
Demand connection (Viewability Server)
- 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
Reporting metrics guide
Traffic source segmentation
We use our own proprietary technology to segment users to the different traffic sources, we are currently offering both ad supply configuration and Reporting data per this segmentation. Currently we divide the users in to 3 categories – Social, Search & Direct. The segment is per the user entire session (e.g User coming from Facebook and browsing 3 pages is considered a social user for all 3 pages).
We are segmenting user behavior per different metrics, but we not segmenting users as audience (we are not trying to replace your DMP, we can actually integrate with it to give you better support for the demand side), we are exploring the possibility of doing that but we prefer to focus on supplying the best inventory based on user engagement and page layout metrics that has being proved to work very good.
Other than that we are recognizing returning users, and tracking the ad density, engagement, page layout and many more per user, session and a single page.
Time on page / session duration
We are constantly monitoring the time users spends on a single page as well as the complete session duration of each user, we use our own proprietary technology to make this and use those metrics in real time to optimize our engine. As for all the data – We display everything on our daily reporting system.
We benchmark a part of the traffic to understand how users react to the locations Browsi is responsible for, we learn that data and constantly making teaks to the engine to improve the locations, we also display that benchmark data we collect anywhere in the reporting. Our benchmark mechanism is usually between 1%-5% of the traffic and configurable, session level based.
Page level optimization
Our optimization and data is always page level based – Meaning that the data we collect and the optimization we do is per page so that the locations of the placements will suit a specific article perfectly and will always be reactive to the way users engage with that page.