Header Wrappers
Overview
The Wrapper dataset contains information about Publisher “Header Bidding” or “Wrapper” solutions. This includes the presence of multiple wrappers on a publisher’s site, as well as the SSP adapters and Identity Providers that a publisher has chosen to implement. Note that the fields installed_modules and user_modules can be quite large. It is helpful to use this dataset in conjunction with the mapping_modules dataset.
Dataset
| Field | Type | Description |
|---|---|---|
| id | integer | identifier for the for wrapper object. |
| publisher_id | integer | publisher identifier that the wrapper corresponds (is installed) on. |
| wrapper_type | string | What kind of wrapper is present? options include pbjs (Prebid, Zeus, IX library, or Amazon (amz_aps)) - this field represents a raw pull of what’s detected on page, versus the normalized dataset found in the mapping_wrappers dataset. |
| version | string | the declared version of a given header bidding solution. |
| user_modules | array | collection of user_modules that are installed on the publisher. |
| installed_modules | array | For Prebid publishers, list of the installed modules found within the publisher’s wrapper. Includes RTB, Consent, and other non-identity modules. |
| last_detected | date | date when the wrapper was last detected. |
| created_at | datetime | Date when wrapper was first scanned by the Sincera platform. |
| updated_at | datetime | Date when wrapper was last updated by the Sincera platform. |
| wrappers_config | jsonb | Provides wrapper configuration details specific to given publisher implementation (i.e. schain, paapi, ortb2, userSync, consentManagement, etc). |
| in_iframe | boolean | Detects whether wrapper is found on top DOM or in a nested iFrame within the page. |
| last_iframe_name | string | Detects the iFrame location on page where Prebid is detected. |