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
Engine UX rules overview
What kind of UX rules can Browsi factor in?
Browsi’s engine looks for ad placements on the page with a set of predefined rules. These rules are rooted in thorough research and experience with mobile web/app content pages – including the diverse ways in which users consume content. Rule application may vary due to page layout and publisher request.
Browsi can incorporate custom rules upon Publisher’s request beyond the standard rules below:
- Fold Limitation – The engine will limit the page area by executing a set of tests to identify the content on the page and all other elements. Browsi will not embed ads on the first fold or inside the footer as this is perceived as bad user experience.
- Distance – The engine sets a distance between each ad on the page, so ads will never be close to one another. Specific distance may vary on pages and sites.
- In-line ads – All in-line ads on the page are identified by the engine and marked as “publisher ads” – this enables our engine to stay away from those placements and to maintain a strong experience for the user. To reiterate the point in #2, distance can vary across sites and pages.
- Monetization solutions – The engine detects most of the monetization solution out there and can incorporate new ones. As a result, Browsi knows what is running on page and can react accordingly. Each solution is treated uniquely according to its functionality and any custom rules.
- Content recommendation platforms – All large content recommendation platforms and their restrictions are recognized by the engine, and the engine will never embed an ad inside a widget or immediately adjacent.
- Video players & images – The engine identifies all video players on page and avoids video ads (outstream) and players in general. The engine identifies images (when served using html image tag) and avoids them as well.
- Paragraphs – Browsi tends to target between paragraphs, however different locations may emerge if rules allow. In all cases, the engine will never break a paragraph or text.
- Social Widgets – Browsi identifies social widgets but does not necessarily avoid them if the engagement around the social widget meets data requirements.
- Comment sections – The engine identifies comment sections and will never embed an ad in one.