Documentation Updates 2015 documentation-updates
A list of new and revised Audience Manager documentation released in 2015. Includes minor updates or changes to the Audience Manager guide that might not be included in the Experience Cloud release notes.
November, 2015 nov-15
October, 2015 oct-15
d_cid or d_cid_ic instead of d_dpid and d_dpuuid. The DPID and DPUUID variables will continue to work, but you should consider them deprecated. This includes DPID and DPUUID variants without the d_ prefix.d_cid and d_cid_ic key-value pairs.September, 2015 sept-15
August, 2015 aug-15
The context data variable ended incorrectly with a dot instead of an underscore.
- Correct:
c_contextData.* - Incorrect:
c_contextData_*
Analytics customers need to set an integration code when using the Master Marketing Profile and passing declared IDs through the Visitor ID service to Audience Manager.
This document is deprecated and has been replaced by Create a Cross-Device Data Source.
July, 2015 july-15
June, 2015 june-15
- Removed the optional parameter,
iframeAttachmentDelay. - Added a note to
declaredIdvariable. When using the Visitor ID Service, set the ID withsetCustomerIDsinstead of DIL. See Customer IDs and Authenticated States.
May, 2015 may-15
Revisions:
- Simplified steps and directions for creating a group and assigning permissions.
- Added information about Wild Card Permissions and how to use them.
April, 2015 apr-15
Added following note:
Note: Audience Manager does not support .zip files for inbound S3 buckets.
March, 2015 march-15
Added a new FAQ that explains why the number of successfully processed records might differ when comparing the Inbound receipt and reporting in AAM.
Added a new FAQ that explains why the trait uniques for my cross-device onboarded traits are higher than the total number of onboarded records.
Removed information about Talend.
Removed information about Netezza and replaced it with information about RedShift.
New topic.
Changed to Privacy and Data Retention FAQ (12/2016).
February, 2015 feb-15
Added information explaining how the delta change is calculated depending on the chosen time frame.
Added a note explaining how to investigate an unusually large delta change in unique visitors.
Added the following information to the Limitations and Rules section:
-
Frequency-capping expressions include all the users whose number of trait realizations is below a desired value.
For example:
frequency([1000T]) <= 5This expression includes all users that have realized the trait with the ID "1000" fewer than five times, including users who have not realized the trait.
-
When you need recency/frequency requirements to be less than a specific number of times or days, you must join that trait to another with an AND operator.
Using the above example,
frequency([1000T]) <= 5, the expression becomes valid when joined with another trait.For example:
frequency([1000T]) <= 5 AND isSiteVisitorTrait -
For advertising frequency-capping use cases, you could create a segment rule similar to the following:
(frequency([1000T] <= 2D) >= 5)?This expression includes all users that have realized the trait with the ID "1000" in the last 2 days more than five times.
You can achieve the capping by sending this segment to the ad server and then include a NOT on the segment in the ad server. This approach achieves greater performance in Audience Manager, while still serving the same purpose for frequency capping.
January, 2015 jan-15
Clarified the amount of time is takes for inbound data to be propagated to the edge.
Significantly edited topic.
Added additional step to explain how to add the use of Declared IDs to DIL and the Mobile SDK.
This document has been deprecated and replaced by Create a Cross-Device Data Source.
Updated text and added illustrations.
This document has been deprecated and replaced by Profile Link.