Integrate with the Prebid Analytics API

This page has been updated for Prebid 1.0. It adds the requirement for a markdown file containing the maintainer’s contact info. Note also that there are a couple of new bidResponse attributes that may be of interest to analytics providers: bid currency and bid gross-vs-net.

The Prebid Analytics API provides a way to get analytics data from Prebid.js and send it to the analytics provider of your choice, such as Google Analytics. Because it’s an open source API, you can write an adapter to send analytics data to any provider you like. Integrating with the Prebid Analytics API has the following benefits:

Architecture of the Analytics API

Before we jump into looking at code, let’s look at the high-level architecture. As shown in the diagram below, Prebid.js calls into an analytics adapter. The analytics adapter is the only part of the code that must be stored in the Prebid.js repo.

The analytics adapter listens to events and may call out directly to the analytics backend, or it may call out to an analytics library that integrates with the analytics server.

For instructions on integrating an analytics provider, see the next section.

Prebid Analytics Architecture Diagram

Integrate an Analytics Provider

You can integrate an analytics provider using the steps outlined below. In the example we’ll use Google Analytics for simplicity, but you can integrate any analytics provider you like as long as you have an adapter and any necessary libraries.

If you want to see how to write your own analytics adapters, look in the repo under modules.

Summary of the steps involved:

Plan the site integration

Some analytics adapters may require the publisher to load a library in the page. If this is the case for your analytics adapter, consider providing an example for users.

For example, to use Google Analytics, publishers must load the Google Analytics library:

    (function (i, s, o, g, r, a, m) {
i['GoogleAnalyticsObject'] = r;
i[r] = i[r] || function () {
(i[r].q = i[r].q || []).push(arguments)
}, i[r].l = 1 * new Date();
a = s.createElement(o),
m = s.getElementsByTagName(o)[0];
a.async = 1;
a.src = g;
m.parentNode.insertBefore(a, m)
})(window, document, 'script', '//www.google-analytics.com/analytics.js', 'ga');

ga('create', 'GOOGLE-ANALYTICS-ID', 'auto');

(See the Google docs for up-to-date instructions.)

A call to pbjs.enableAnalytics(analyticsAdapters) is needed to initialize the module(s). It should be called once on the page, after any analytics libraries have been loaded. Note that more than one analytics adapter can be loaded, though this isn’t necessarily recommended.

pbjs.que.push(function () {
pbjs.enableAnalytics([{
provider: 'ga',
options: {
enableDistribution: false
}
},{
provider: 'abc',
options: {
account: 'ABC-ACCOUNT-ID',
endpoint: 'https://...'
}
});
}]);
});

Create the Prebid.js analytics module

Step 1: Add a markdown file describing the module

  1. Create a markdown file under modules with the name of the bidder suffixed with ‘AnalyticsAdapter’, e.g., exAnalyticsAdapter.md

Example markdown file:

# Overview

Module Name: Ex Analytics Adapter
Module Type: Analytics Adapter
Maintainer: prebid@example.com

# Description

Analytics adapter for Example.com. Contact prebid@example.com for information.

Step 2: Add analytics source code

Breaking changes for Prebid 1.0
There are two breaking changes to the data emitted from analytic events for Prebid 1.0:

  1. Events that previously emitted a requestId property now emit that data as the auctionId property
  2. The BID_TIMEOUT event that previously emitted an array of bidder code strings now emits an array of objects containing bidId, bidder, adUnitCode, and auctionId for timed out bids

  3. Create a JS file under modules with the name of the bidder suffixed with ‘AnalyticsAdapter’, e.g., exAnalyticsAdapter.js

  4. Create an analytics adapter to listen for Prebid events and call the analytics library or server. See the existing *AnalyticsAdapter.js files in the repo under modules.

  5. There are several types of analytics adapters. The example here focuses on the ‘endpoint’ type. See AnalyticsAdapter.js for more info on the ‘library’ and ‘bundle’ types.

    • endpoint - Calls the specified URL on analytics events. Doesn’t require a global context.
    • library - The URL is considered to be a library to load. Expects a global context.
    • bundle - An advanced option expecting a global context.
  6. In order to get access to the configuration passed in from the page, the analytics adapter needs to specify an enableAnalytics() function, but it should also call the base class function to set up the events.

A basic prototype analytics adapter:

import {ajax} from 'src/ajax';
import adapter from 'src/AnalyticsAdapter';
import CONSTANTS from 'src/constants.json';
import adaptermanager from 'src/adaptermanager';

const analyticsType = 'endpoint';
const url = 'URL_TO_SERVER_ENDPOINT';

let exAnalytics = Object.assign(adapter({url, analyticsType}), {
// ... code ...
});

// save the base class function
exAnalytics.originEnableAnalytics = exAdapter.enableAnalytics;

// override enableAnalytics so we can get access to the config passed in from the page
exAnalytics.enableAnalytics = function (config) {
initOptions = config.options;
exAnalytics.originEnableAnalytics(config); // call the base class function
};

adaptermanager.registerAnalyticsAdapter({
adapter: exAnalytics,
code: 'exAnalytic'
});

Analytics adapter best practices:

  • listen only to the events required
  • batch up calls to the backend for post-auction logging rather than calling immediately after each event.

Build the package

To add the new analyticsAdapter into a prebid package, use a command like this:

gulp bundle --modules=exAnalyticsAdapter,xyzBidAdapter

Further Reading