Data Action Components data-action-components
Data action components include Customer Data Feeds, the Data Collection Server, SFTP/S3/HTTP publishers, IRIS, and the Profile Cache Server.
Action components are systems and processes that let you move data in and out of Audience Manager and (for the lack of a better phrase) do things with it. These Audience Manager components include:
Customer Data Feeds (CDF) cdf
CDF are files sent hourly to customers. These contain user IDs along with associated segment IDs, trait IDs, and other data. For more information, see Customer Data Feed Overview.
Data Collection Server (DCS) dcs
See Data Collection Components.
SFTP/S3 sftp-s3
The SFTP/S3 publishers receive synchronized ID data from the Outbound Feed Converter. When these files are ready, the SFTP/S3 publishers send this data to a destination specified by the client. These files contain synchronized ID data with a one-to-many mapping of Audience Manager user IDs (UUID) to:
- Device ID/data provider IDs (DPUUID)
- Qualified segment IDs
- Trait IDs
Audience Manager customers do not have access to features that directly control the SFPT/S3 publishers. Customers use this service indirectly when they create and send data to destinations. The SFTP/S3 system is, essentially, an automated job process that runs at scheduled intervals.
IRIS iris
In Greek mythology, Iris is a figure who travels and delivers messages rapidly. The IRIS system is a namesake that reflects the characteristics of this figure from the ancient world. In modern terms, IRIS is a low-latency, high-frequency cookie synchronization and data transfer service.
IRIS works with the same type of data as the SFTP/S3 system. However, IRIS is different because it sends data to destinations in real time rather than at set intervals. This is a separate system because the SFTP/S3 publishers can’t send data to an HTTP destination and they’re not designed for real-time data transfers.
There are no UI controls that let customers work directly with IRIS. Customers work with IRIS indirectly when they create and send data to destinations, and for other processes that require rapid data transfers.
Examples of IRIS services and features include:
-
Providing fast (within 30 seconds) synchronization for cookies and segments. It can synchronize the Audience Manager cookie, partner cookies, or both.
-
Real-time data transfers. IRIS is responsible for sending real-time segment qualification events to a partner or other destination. This data is JSON-formatted and sent via an HTTP
POST
request. -
Bulk server-to-server data transfers: If you exchange large amounts of data with Audience Manager, IRIS is the system that your servers engage with to transfer data.
-
Reliable infrastructure that works at scale and is fault tolerant. Systems that power IRIS include Amazon SQS, Amazon EC2, and Cassandra.
Segment Mapping Rules
To optimize traffic between IRIS and segment destinations, IRIS sends segments to destinations based on a set of rules.
-
New segment qualification: when a device qualifies for a new segment, IRIS sends all segments associated to that device to all of the destinations mapped to these segments.
-
New segment disqualification: when a device no longer qualifies for a segment, IRIS sends all segment qualifications and disqualifications associated to that device to all of the destinations mapped to these segments.
-
Destination mapping updates: when a destination mapping is updated, IRIS sends all segments associated to a device to all of the destinations mapped to these segments, the next time Audience Manager sees the device.
-
Device graph updates: when any device ID gets added or removed from the device graph used to evaluate a segment, IRIS sends all segments associated to that device to all of the destinations mapped to these segments, the next time Audience Manager sees the device.
Sample data file
The following example contains real-time segment data from IRIS. Keep in mind this is sample data only. Each customer may have different formatting requirements so the contents can vary.
{
"ProcessTime": "Tue Jul 21 19:12:45 UTC 2015",
"Client_ID": "111111",
"AAM_Destination_Id": "22222",
"User_count": "5",
"Users": [
{
"AAM_UUID": "28272096202945091600036434734793744071",
"DataPartner_UUID": "CAESEFdv5pk-Lurd8vL9Yfb3qFg",
"Segments": [
{
"Segment_ID": "1200598",
"Status": "1",
"DateTime": "Tue Jul 21 19:12:12 UTC 2015"
}
]
},
{
"AAM_UUID": "35183292386788708387827965829455926157",
"DataPartner_UUID": "CAESEF_d8blvZjchQ2WTzdB65yk",
"Segments": [
{
"Segment_ID": "1306742",
"Status": "1",
"DateTime": "Tue Jul 21 19:12:15 UTC 2015"
}
]
},
{
"AAM_UUID": "28012470144260632050402316345856327572",
"DataPartner_UUID": "CAESEEPfHBiRjhkzvBPXQ-0MFRE|UzCESAAABOnFeHJy",
"Segments": [
{
"Segment_ID": "1306742",
"Status": "1",
"DateTime": "Tue Jul 21 19:12:33 UTC 2015"
}
]
},
{
"AAM_UUID": "18981483751565214534184221210627150539",
"DataPartner_UUID": "CAK4NDH0ESEE6NBEhoWDkB7s7ZY|VPYFQQAAASXPElL0",
"Segments": [
{
"Segment_ID": "1306742",
"Status": "1",
"DateTime": "Tue Jul 21 19:12:36 UTC 2015"
}
]
},
{
"AAM_UUID": "04761851136483019318109155624251711702",
"DataPartner_UUID": "CAESEDkM5aSaKMV8MfaBhgSspmE|VYnTNwAAASzvVhxy",
"Segments": [
{
"Segment_ID": "1306742",
"Status": "1",
"DateTime": "Tue Jul 21 19:12:42 UTC 2015"
}
]
}
]
}