Salesforce Audience Studio allows publishers and marketers to collect and organize consumer web data in one central "big-data" warehouse. Using Audience Studio, 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 Audience Studio.
The "raw" consumer web data collected in Audience Studio can be analyzed and combined into Audience Segments using Audience Studio’s Segment Builder. Audience Studio users can then use these audience segments to customize content and advertising, and commerce offers on their websites.
Please note that Audience Studio enforces a 90-day expiration for all files and data on our customer and partner-accessible AWS S3 buckets. Each day's delivery is the latest complete data set from your Audience Studio instance.
Standard Data Feeds
The Standard Data Feed provides 2 file sets by default and an additional user match table upon request:
- User Audience Segment Map (full refresh) - Export of all users and the segments they are a part of.
- Segment Mapping - Export of all segment IDs and mapping to segment name along with last computed date.
- 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.
Audience Studio 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:
- De-normalized (all segments for a user are listed in one row):
- Krux User ID
- Publisher User ID (if publisher user-matching has been enabled)
- Segment List: comma-separated list of Segment IDs
- Normalized (each segment for a user is listed in a separate row):
- Krux User ID
- Publisher User ID (if publisher user-matching has been enabled)
- Segment ID
Sample De-normalized Audience Segment Map:
CLICK TO SCROLL and view entire sample
**Format**
KruxUserID^PublisherUserID^SegmentID_1,SegmentID_2
**Data**
H-BzegqK^-^KnfkKSYc,1b0_qwR,5XA_2BUt,5XAtRS,KgtK_2l9,KgtKkKE4,Kss_6Ciu,K5_UmfGe,K1eGkSX7,KE7d7WS8,Khs2HmA2,K9o8e4vw,K1910ueg
H-DNsgaE^-^KEhUTKLA,KIzIsBb6,KfYWnVIY,KIDInF9L
H01MOZfa^-^Khs1CKxP,KgsrHKRm,KgsreNBQ,KermxnBE,Kfb8bgPE,KgsxR3Oe,KIdHqzYg,Khs3HmA2,KIDInF9L
H12Thbgl^-^KvKR03uf,Kf0KqZ9L,KIDIrF9LSample Normalized Audience Segment Map:
CLICK TO SCROLL and view entire sample
**Format**
KruxUserID^PublisherUserID^SegmentID
**Data**
004326160e9994bd6f3f4e30270a5dc8^-^KzzFYzb1
00182006a6xbe3ibd4ledc2c0eb59z04^-^KyBA51Ud
00182006a6xbe3ibd4ledc2c0eb59z04^-^K3r1VWTE
PLEASE NOTE: Audience segment map exports by default export the "short" format of the KUID in the 1st column. This is the KUID we use to identify devices in our platform across browsers, mobile apps, OTT devices, etc.
We also have the option to export the "long" format of the KUID. This KUID typically shows up if you are a publisher passing the KUID to your DFP ad calls for the purposes of DFP ad log ingestion into Audience Studio. It's a lowercase KUID since Google requires key-values in DFP ad calls to be lowercase.
We can configure if requested which KUID version should export - long, short, or even both. If you do decide to have both KUIDs export, please note that they will both appear in the 1st column of this export separated by a pipe delimiter.
The User Audience Segment Map does not include platform segments. Given that user lists for platform segments are uploaded by our clients, the mapping of users per platform segment is already available to the client.
Segment mapping file
Audience Studio 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
**Format**
Category,SubCategory,Type,Name,SegmentId,SegmentIdLong,Last Compute Day,Description
**Data**
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, Audience Studio 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
**Format**
UserIDAttribute^FirstPartyUserID^KruxUserID^Timestamp
**Data**
login_id^1234567^K1Y4v5tg^1480087480
login_id^9876543^K6T1mqSD^1480088069
login_id^4567890^K6TV_3SG^1480088126
login_id^7654321^K54urHXH^1480099969
login_id^3452123^K6o2cUJq^1480100645
For additional info see: Standard Data Feed Technical Specification Sheet
0 Comments