Standard Data Feed

The Salesforce Data Management Platform (DMP) allows publishers and marketers to collect and organize consumer web data in one central "big-data" warehouse. Using the Salesforce DMP, it’s possible to consolidate and reconcile first party "web-behavior" data that is generated by consumers as they browse. Publishers and marketers can also integrate data from their user registration and subscription databases into the Salesforce DMP.

The "raw" consumer web data collected in Salesforce DMP can be analyzed and combined into Audience Segments using Salesforce DMP’s Segment Builder. Salesforce DMP users can then use these audience segments to customize content and advertising, and commerce offers on their websites.

Standard Data Feeds

The Standard Data Feed provides 2 file sets by default and an additional user match table upon request:

  1. User Audience Segment Map (full refresh) - Export of all users and the segments they are a part of.  
  2. Segment Mapping - Export of all segment IDs and mapping to segment name along with last computed date.
  3. First Party Usermatch Table (Upon request) - Export of all first party user ids mapped to a Krux User ID.

Each extract is available as a Caret (^) Separated Value file (CSV) and can be shared with the client via Krux's Amazon S3 account.  The client can then pull files from their client-specific location.

Salesforce DMP will deliver one or more files to client specific S3 bucket. Delivery location will remain constant, though number and naming of files may vary due to back end processing.

The formats of each extract are listed below:

User Audience Segment Map

The Audience Segment Map includes segments that have been computed in the last 14 days. The user audience segment map is available in 2 formats:

  1. De-normalized (all segments for a user are listed in one row):
    1. Krux User ID
    2. Publisher User ID (if publisher user-matching has been enabled)
    3. Segment List: comma-separated list of Segment IDs
  2. Normalized (each segment for a user is listed in a separate row):
    1. Krux User ID
    2. Publisher User ID (if publisher user-matching has been enabled)
    3. Segment ID

Sample De-normalized Audience Segment Map:

CLICK TO SCROLL and view entire sample



Sample Normalized Audience Segment Map:

CLICK TO SCROLL and view entire sample



Segment mapping file

Salesforce DMP also provides a mapping file that maps SegmentIDs to Segment Names. The mapping file has the following columns:

  • Category
  • Sub Category
  • Type
  • Name
  • Segment ID
  • Segment ID Long
  • Last Compute Day
  • Description

Sample Segment Mapping File:

CLICK TO SCROLL and view entire sample

Category,SubCategory,Type,Name,SegmentId,SegmentIdLong,Last Compute Day,Description

Category,SubCategory,Type,Name,SegmentId,SegmentIdLong,Last Compute Day,Description
,,TEST,TEST001_ Xeneto in Lia,B8Y6OuXS,qscm4r5es,2015-11-20,First segment to test DMP (MKT)
,,TEST,TEST002_ Torrier at Ferlin,B94VLqBk,qtnqle84m,2015-11-20,Second segment (Fab)
TEST,,TEST,Tut Suit - Test OD,B95rgPLR,qtodBnyv3,2015-09-16,Test On Demand on standard segment activation - DF

First Party Usermatch Table

Upon request, Salesforce DMP can also provide a User Match Table holding the mapping of Krux User IDs and the latest first party user ID associated with them.

  • Sample First Party Usermatch File:

CLICK TO SCROLL and view entire sample



For additional info see:
 Standard Data Feed Technical Specification Sheet

Have more questions? Submit a request


Article is closed for comments.