Page tree
Skip to end of metadata
Go to start of metadata

Introduction

Adhese Gateway (GW) logs all actions it takes during the process of receiving a request from a device and returning a response milliseconds later. This data is made available to the Gateway users, through BigQuery (BQ) tables that contain results per day and are updated at midnight. 

The BQ tables are subject to change, so make sure that if you implement against them, you are ready to configure changes in the columns' structure. Planned changes will be communicated before any deployments, but we will not wait for each implementer to update.

Access your Adhese data

As a customer, you can get access to your data in 3 different ways, each suitable for its own use case, briefly described below:

  • Through a predefined Google data studio report

There are standard data studio templates available which we can connect to your data source. 

This will give you immediate insights without any hassle or development. 

  • Access to the data studio data source(s)

This will allow you to create your own custom dashboards. 

Useful to report on specific cases that are not covered by the standard dashboards.

  • Direct access to the BigQuery table(s)

The more advanced option to query the dataset(s) directly or export them. 

This requires some technical knowledge.


If you would like to access your data through any of these ways, please contact support@adhese.eu and provide a (Google) email address we can share access with. 

Through a Google data studio template

At Adhese, we have a variety of predefined dashboards available to provide immediate insights into your data. Some examples are shown below.

Access to the data studio data source(s)

Another possibility is to get access to the underlying data sources directly. This allows you to create any kind of custom report or dashboard. When working with the data, it is important to understand the different columns and how they should be interpreted. 

Direct access to the BigQuery table(s)

This is the more advanced option for your data team and allows you to directly query the data sources or export the data to your own data solution. 

To access the BigQuery source, the following steps are required:

  1. Reach out to support@adhese.eu, and provide a Google email address connected to a google cloud account. We’ll provide the required permissions.
  2. Once access is provided, you can query the different tables.
  • Make sure you are within your own google cloud project; otherwise, errors will be returned.
  • Make sure you are using the right data-location, by default this is europe-west2.

    

The table names are structured as follows: adhese-cloud.${customer}.${table_name}

Where ${customer} is your Adhese account name and  ${table_name} is the table you are trying to query. See details about the different tables below. 

Your Adhese account name can be found in the URL used to login to the Adhese platform (e.g. https://demo.adhese.org/)

A test query could look as follows:





If this works, you should be able to use any BigQuery functionality to process your data further. 

In case you still have any questions, please don’t hesitate to contact us at support@adhese.eu 

Overview of Collected Data

During the lifetime of a single GW request/response, two sets of data are collected, the Media set and the Market set.

The Media set contains all information on the request, which device it originated from, what content is associated with, which user is linked to it (if any), ... . The exact attributes of the Media set are different for each GW account, depending on the available data and context an account has configured.

The Market set contains the communication log between GW and the active markets for a given GW account. Market standards determine available attributes, although some attributes are not available at all markets. The Market set contains all incoming Bid Responses from all active markets, with advertiser and pricing info.

Table descriptions

slots_extended (adhese-cloud.${customer}.slots_extended)

This table contains the Market data set. Each row in the table contains a number of bid responses per day, aggregated in latency buckets of 10ms.

Field name

Type

Mode

Description

date

DATE

NULLABLE

The date on which these bid requests were received.

slot

RECORD

NULLABLE


slot. id

INTEGER

NULLABLE

The ID of the slot the bid request was made from.

slot. code

STRING

NULLABLE

The code of the slot the bid request was made from.

publication

RECORD

NULLABLE


publication. name

STRING

NULLABLE

The publication name in the Adhese dbase.

publication. url

STRING

NULLABLE

The publication URL in the Adhese dbase.

format

RECORD

NULLABLE


format. name

STRING

NULLABLE

The format name in the Adhese dbase.

format. width

INTEGER

NULLABLE

The format width in pixels for this Bid Response.

format. height

INTEGER

NULLABLE

The format height in pixels for this Bid Response.

publisher

RECORD

NULLABLE


publisher. name

STRING

NULLABLE

The name of this location in the Adhese dbase.

market

RECORD

NULLABLE


market. name

STRING

NULLABLE

The market instance name as known in the Adhese configuration.

market. currency

STRING

NULLABLE

The currency this market uses for bid responses.

bid

RECORD

NULLABLE


bid. count

INTEGER

NULLABLE

The number of bid responses for this record.

bid. amount

FLOAT

NULLABLE

The total value of the bid responses for this record, in market.currency.

bid. winning

RECORD

NULLABLE


bid.winning. count

INTEGER

NULLABLE

The number of winning bid responses for this record.

bid.winning. amount

FLOAT

NULLABLE

The total value of the winning bid responses for this record, in market.currency.

bid. tracked

RECORD

NULLABLE


bid.tracked. count

INTEGER

NULLABLE

The number of rendered bid responses for this record. (aka. paid impressions)

bid.tracked. amount

FLOAT

NULLABLE

The total value of the rendered bid responses for this record, in market.currency.

seatId

STRING

NULLABLE

The seat ID as known by this market.

domain

STRING

NULLABLE

The "OpenRTB adomain" field, containing the domain of the advertising party or brand for this Bid Response.

dealId

STRING

NULLABLE

The deal ID as known by this market.

crId

STRING

NULLABLE

The creative ID as known by this market.

discountRate

FLOAT

NULLABLE

The value of the multiplier applied to this bid response.

exchangeRate

FLOAT

NULLABLE

The value of the exchange rate at the moment of the bid between market.currency and EUR.

latency

INTEGER

NULLABLE

The value of the latency bucket for these bids.

deviceType

STRING

NULLABLE

The label of the device that generated the bid request (phone, desktop, tablet, tv).

consent

BOOLEAN

NULLABLE

Indication of consent for the bid requests to this market.


access_log (adhese-cloud.${customer}.access_log)

This table contains direct ad server and campaign data. 

Field Name

Type

Mode

Description

date

DATE

NULLABLE

The date on which these requests were received.

slot

RECORD

NULLABLE

 

slot. id

STRING

NULLABLE

The Adhese ID of the slot or placement requested

slot. code

STRING

NULLABLE

The string used in the client application to request this slot.

publication

RECORD

NULLABLE

 

publication. name

STRING

NULLABLE

The name of the publication in the Adhese dbase.

publication. url

STRING

NULLABLE

The URL of the publication in the adhese dbase.

format

RECORD

NULLABLE

 

format. name

STRING

NULLABLE

 

format. width

INTEGER

NULLABLE

Width of the format in pixels.

format. height

INTEGER

NULLABLE

Height of the format in pixels.

publisher

RECORD

NULLABLE

 

publisher. name

STRING

NULLABLE

The name of the section in Adhese dbase.

bid

RECORD

NULLABLE

 

bid. amount

INTEGER

NULLABLE

Number of bids.

bid. tracked

RECORD

NULLABLE

 

bid.tracked. amount

INTEGER

NULLABLE

Number of rendered ads (aka. paid impressions)

bid. clicked

RECORD

NULLABLE

 

bid.clicked. amount

INTEGER

NULLABLE

Number of clicked ads.

creative

RECORD

NULLABLE

 

creative. name

STRING

NULLABLE

Adhese creative name.

creative. id

INTEGER

NULLABLE

Adhese creative ID.

campaign

RECORD

NULLABLE

 

campaign. name

STRING

NULLABLE

Adhese campaign name.

campaign. id

INTEGER

NULLABLE

Adhese campaign ID.

booking

RECORD

NULLABLE

 

booking. id

INTEGER

NULLABLE

Adhese booking ID.

booking. pricing

RECORD

NULLABLE

 

booking.pricing. type

STRING

NULLABLE

Adhese booking price type (CPM, CPC, CPD, …).

advertiser

RECORD

NULLABLE

 

advertiser. id

INTEGER

NULLABLE

Adhese advertiser ID.

advertiser. name

STRING

NULLABLE

Adhese advertiser name.

actions

STRING

REPEATED

Array of events that were triggered for a given rendered ad. Contains for example items like “start, mute, skip, …” for video completion events.

targets

RECORD

NULLABLE

Custom list of targets as set up by the Adhese account configuration. Contains data like user information, contextual data, device info, …

targets. br

STRING

REPEATED

 

targets. dm

STRING

REPEATED

 

targets. dt

STRING

NULLABLE

 

targets. og

STRING

NULLABLE

 

targets. tl

STRING

NULLABLE

 

targets. ge

STRING

NULLABLE

 



adfill_rate (adhese-cloud.${customer}.adfill_rate)

This table contains ad request data.

Documentation coming soon, ask support@adhese.eu for more info if needed. 



  • No labels