Data Transfer File 2.0 Import

This documents explains requirements and process to ingest Data Transfer Files 2.0 (DT 2.0) from Google to Salesforce DMP.

Important note: DT 2.0 implementation does not replace media tag implementation, as the KUID is not captured in DT 2.0 files. In order to capture full value from the platform powered by processes such as user match, media tag implementation is required.

Why use DT 2.0?
Trade-Offs
Prerequisites
Process for Salesforce DMP to Enable Log Access
File Types to Ingest
Google Reference Documentation

Why use DT 2.0

DT 2.0 files enables supplemental data ingestion for those brands that are buying inventory through GDN. In all cases, tagging is the best practice to ensure proper user matching across channels. If your organization has limited to no Ad Ops or Agency support, DT 2.0 file ingestion may be used to feed your campaign and impression data into the platform.

Trade-Offs

  • If media tagging is bypassed in favor of DT2.0, key functionality will be compromised.

Data Not in DT2.0

Salesforce DMP Functionality Lost

confID

User Matching

deviceID (MAIDs)

Channel (Display, Video, In-app, Paid Search, Social)

Segments by channel, overlap analysis

Campaigns targeted by Google Audiences are not available in log feed

Visibility into a portion of campaigns

 

  • Google Data Transfer is at cost. Please contact your Google Account Manager for pricing specifics.
  • DT 2.0 standardized files that cannot be customized. The format desired contains 103 fields, the Unified DCM//DBM file. Please contact your Google Account Manager if your file contains less than 103 fields.
  • DT 2.0 is only available for DCM. DCM – includes: DBM - advertisers buying for marketers not using DCM, Display Campaign Report (includes AdWords (not search), YouTube, GDN/Adsense)

 

Data Not in DT2.0

Salesforce DMP Functionality Lost

confID

User Matching

deviceID (MAIDs)

Channel (Display, Video, In-app, Paid Search, Social)

Segments by channel, overlap analysis, journeys

Campaigns targeted with Google Affinity Audiences

Lost visibility into a portion of campaigns

Prerequisites

  1. Evaluate costs:  Is there enough data to build segments? If media tracking by publishers is under 5%, then DT 2.0 may be needed.
  2. Understand the data available in each feed. DT 2.0 is limited to DCM clients only, additional work is needed to ingest GDN and YouTube. Please consult your Google Account Manager to understand the extent of  any of your feeds. Any Google Affinity Audiences targeted is not available, as a result it may yield one or more logs useless.
  3. Evaluate if enough data is available to justify a Salesforce DMP DT 2.0 implementation
  4. Agree to contractual terms with Google
  5. Create a Google Cloud Storage bucket.Salesforce DMP can accept multiple buckets.
  6. Complete pre-work with Google before engaging in Salesforce DMP DT 2.0 implementation.

Process for Salesforce DMP to enable log access

  1. Request contractual terms from Google Account Manager for file transfer access. If you agree to the terms, respond as instructed to confirm agreement. For Salesforce DMP to ingest the data, Salesforce DMP must be specified in one of the two partner slots for log files.
  2. Work with the Google Account Manager to ensure that Salesforce DMP is configured to populate one of the two Partner ID fields ("Partner 1 ID" or "Partner 2 ID"). The value will be Krux’s (Salesforce DMP) Google ID.  Verify value with the Google Account Manager.  DT2 files will be processed only if that Partner ID is present.
  3. Designate a Google Group for your Advertiser. (A specific Google Account can be granted access as well, but a Google Group will allow you to grant access to multiple users.)

Steps for setting up a Google Group:

  1. Go to the Google Group site
  2. Click on the Create Group button, near the top left corner of the page
  3. Fill out the form
      • In the Basic Permissions section, make sure the posts are private. For more information on the permissions, see the Google support page.
  4. Click the Create button at the top of the page
  5. Once the Google Group is created, invite the Salesforce DMP address googledataxfer@krux.com to group.
  6. Contact Salesforce DMP to verify DT2 files and begin imports.

Types to Ingest:

  • Clicks
  • Activity
  • Campaigns
  • Ads
  • Advertisers
  • Placements
  • Sites
  • Impressions

There are four different files that DT 2.0 may deliver for a client depending on what data is needed: 1) a DBM only file, 2) a DCM only file, 3) a unified DCM/DBM file, 4) and an AdWords file.  (The AdWords file is currently called the Display Campaign Report.)  The Google Account Manager will be filling out a form that is similar to the following (this one is for the Unified DCM//DBM file: example file attached):

 

DCM/DBM DT Form  Last Updated 01/26/2016

Data Transfer Account Configuration:

 

DCM Account Name:

<required>

DCM Account ID:

 

DBM Partner Name:

 

DBM Partner ID:

 

DT Type (DCM Only/DBM Only/Unified):

 

DT Level (Network/Floodlight)

 

DCM Floodlight Configuration ID:

<required only if "Floodlight Configuration" is selected above>                                   

DCLK Contact Name:

<required>

Requested Action:  

Select One: create | update | deactivate

Separator stringacter:  

Comma (,)

Google Cloud Storage Bucket Name:

 

Client Google Group:

<Google Group to permission DT files to - see instructions for details>

Compress Files:  

gzip

User ID Encryption ID:

 

Partner 1 ID Encryption ID:

 

Partner 2 ID Encryption ID:

 

Request date:  

YYYY-MM-DD

Required Start date:  

YYYY-MM-DD

End date (Required max 12/31/2016):  

YYYY-MM-DD

Data Availability Period**:  

60

Google Reference Documentation:

Have more questions? Submit a request

0 Comments

Article is closed for comments.