Back to Bidders

Glimpse Protocol

Features

Bidder Code glimpse Prebid.org Member no
Media Types display GDPR TCF Support yes
User IDs none USP/CCPA Support yes
Supply Chain Support no COPPA Support no
Demand Chain Support no GPP Support no
Supports Deals yes Prebid.js Adapter yes
IAB GVL ID 1012 Prebid Server Adapter no
Floors Module Support no First Party Data Support check with bidder
Multi Format Support check with bidder ORTB Blocking Support check with bidder
Safeframes OK check with bidder

"Send All Bids" Ad Server Keys

These are the bidder-specific keys that would be targeted within GAM in a Send-All-Bids scenario. GAM truncates keys to 20 characters.
hb_pb_glimpse hb_bidder_glimpse hb_adid_glimpse
hb_size_glimpse hb_source_glimpse hb_format_glimpse
hb_cache_host_glimps hb_cache_id_glimpse hb_uuid_glimpse
hb_cache_path_glimps hb_deal_glimpse

Overview

Module Name: Glimpse Protocol Bid Adapter
Module Type: Bidder Adapter
Maintainer: support@glimpseportal.io

Description

Glimpse protects consumer privacy while allowing precise targeting. This module connects publishers to Glimpse Protocol’s demand sources via Prebid.js.

Supported Media Types

Type Sizes
Banner 300x250, 300x600, 320x50, 728x90, 970x250

Setup

Prerequisites

Before you start, you will need to build a prebid.js file with the Glimpse module included, and include both gpt.js and prebid.js in the head of each page with supply. An example of a typical pair of script tags might be:

<script
  async
  src="https://securepubads.g.doubleclick.net/tag/js/gpt.js"
></script>

<script async src="https://<PUBLISHER_DOMAIN>/prebid.js"></script>

Configuration

Bid Requests

Our adapter expects the following values in the params block of each bid request:

Name Scope Type Description Example
pid Required string A unique identifier representing an ad unit. It is provided by Glimpse when registering an ad unit. ‘glimpse-placement-id’

Example

const units = [
  {
    code: "ad-unit-0",
    mediaTypes: {
      banner: { sizes: [[300, 250]] },
    },
    bids: [
      {
        bidder: "glimpse",
        params: {
          pid: "glimpse-placement-id",
        },
      },
    ],
  },
]

First Party Data

Our adapter works with first party data providers as described here. In this example we add Permutive data to our bidder request using setBidderConfig.

Example

pbjs.que.push(() => {
  pbjs.setBidderConfig({
    bidders: ["glimpse"],
    config: {
      ortb2: {
        site: {
          keywords: "business,finance,crypto",
          ext: {
            data: {
              permutive: {
                pvc: JSON.parse(localStorage.getItem("permutive-pvc")) ?? {},
              },
            },
          },
        },
        user: {
          ext: {
            data: {
              permutive: {
                keywords: JSON.parse(localStorage.getItem("_psegs")) ?? [],
                enrichers:
                  JSON.parse(
                    localStorage.getItem("permutive-data-enrichers")
                  ) ?? {},
              },
            },
          },
        },
      },
    },
  })
})

FAQs

Can you provide additional support?

Of course! You can check the Glimpse Prebid Adapter documentation at https://docs.glimpseportal.io/en/latest/ or reach out to us at support@glimpseportal.io.

Back to Bidders