Data Onboarding

The Magnite Data Onboarding listing allows you to onboard your first-party or third-party data for activation within Magnite SSPs. The following provides a step-by-step approach for Clients and Data Partners to onboard their data into Magnite. This listing currently supports onboarding data for activation on Magnite Streaming.

To get started, click the request button to email the Magnite Snowflake admin team with more information on the data you want to onboard. Please include:
* Your company name
* A point of contact and email address
* The type of data you want to onboard (first-party/3rd party)
* The data size
* The number of user profiles
* The average number of segments per profile
* Expected frequency of updates.
* Expected size of updates.
* The region where data is located. Note: Magnite requires data to be stored in US-east-1.

A member of our admin team will review the request. Once the request is approved, Magnite will share our target Snowflake account name so you can begin sharing data views with Magnite.

Segment Membership and Taxonomy Table Requirements.
Magnite requires a segment membership and taxonomy table for data onboarding. The following outlines the requirements for each table.

Segment Membership Table Requirements
Field | Data type | Required | Optional | Definition
StorageId | VARCHAR(255) | Required | first-party ID, device ID, or IP
IdType | VARCHAR(36) | Required | First Party ID, IDFA, RIDA, TIFA, AAID/GAID, or IP
SegmentId | VARCHAR(36) | Required | Required even if a publisher and advertiser plan to maintain one master list. One Segment per row.
Active | BOOLEAN | Required | TRUE or FALSE. A user is opted-out when set to FALSE.
UpdateTimestamp | TIMESTAMP | Required | Timestamp of the update to Magnite.

Taxonomy Table Requirements
Field | Data type | Required | Optional | Definition
ClientName | VARCHAR(255) | Required | Data Provider or Publisher or Advertiser Name
AccountId | VARCHAR(36) | Required | Magnite Account ID associated with the client. (This is where the segment needs to go within Magnite.)
DataShareSettings | VARCHAR(36) | Required | Values are Public or Private.
SegmentId | VARCHAR(36) | Required | Segment ID(s) provided in the segment membership table.
SegmentName | VARCHAR(255) | Required | Name of the segment.
SegmentDescription | VARCHAR(255) | Optional | Notes/metadata on the segment. 
SegmentCPM | DOUBLE | Optional | Cost of the segment. This is USD and cents.
Platform | VARCHAR(255) | Required | Magnite Streaming. Eventually, additional platforms will be supported.
Active | BOOLEAN | Required | TRUE or FALSE. Related to segment status.
UpdateTimestamp | TIMESTAMP | Required | Timestamp of update to Magnite.

Data Share Requirements
1. To ensure data is in the correct format, please run the code snippet in the SQL Query section of this listing before sharing data (https://docs.google.com/document/d/e/2PACX-1vR2GuqGfhCHpXodO6vP-I4CP4YE2y5DXxu552b_OPSKU-0rOI_Znb8WdEabgSw2PncxAIs9QhjoY1-j/pub)
2. A stream (change tracking) on the view must be enabled. For more information on this, see https://docs.snowflake.com/en/user-guide/streams-manage or contact Magnite for more information.
3. To make the view accessible to Magnite, please create a share of each table and grant privileges to the shared objects using our target Snowflake account name.

Magnite Data Ingestion
Updates to data shares are checked and ingested into Magnite daily.