Callback Scripts

Introduction

Several triggers can be used by Browsi Player to activate a publisher’s custom script.

These scripts can come in three supported formats.

While they can be used as a flexible solution for many use cases, the most common scenarios are analytics pixels and passbacks.

Triggers

1. Inventory - When the player loads to the page

2. Impression - When an ad starts playing

3. Ad completed - when an ad is played all the way through

4. Player closed - when a used clicks the X button to close the player

5. No ad - trigger a callback script when Browsi Player finishes attempting to play ads

Supported formats

1. GPT - this is the most commonly used format, and will run a Google Publisher Tag you provide us once Browsi Player finishes attempting to play ads.

2. JavaScript - snippets of JavaScript code, which can serve almost any function.

3. Script - a URL that links to your hosted code; similar to a JavaScript format, but gives you more control (i.e. the option to change the implemented script without going through us)

4. Image - also uses a URL, mostly linking to 1X1 pixels.

5. Notify - when a player is set to only run after being activated by a trigger code (i.e. set to a ‘waiting’ state), this makes the player trigger as soon as a previous player finishes.

Use cases

The most common use cases are:

1. Passback - when Browsi Player is no longer able to bring in additional ads, you may want to bring another player or a display placement to the page in its place.

2. Analytics pixel - integrate data solutions on the page with player events as their triggers, for example fire an ‘impression’ event to Google Analytics.