Hi Marc, There are no pre-requisites for the demdex cookie to be set on
the browser. The 3rd party Id sync happens because of settings done
internally by Adobe audience manager per account.Also the visitor does
not need to visit the 3rd party's website to get this done.Best,Rachit
Hi Marc,The partner id sync happens on the 1st visit itself. The
following steps describe how ID matching works when a partner initiates
this process:Identify user: A new visitor arrives on a web property
that's tagged with the partner's media, ads, or data collection
code.Send User ID: Partner's code loads the Audience Manager ID Sync
URL, attaches the partner user ID, and makes a call to Audience Manager
ID Sync URL.Synchronize IDs: Audience Manager receives the call and
matches the user ID to...
Hi Marcin,Audience library created audiences get collected in Audience
manager as well with the rules created as Traits.These Traits have by
default TTL of 120 days.You can change the TTL of the trait in AAM for
the account.Best,Rachit Sachdev
Hi swetak25728373Audience manager currently does not have integration
with Instagram.You can check the list of Partners in the link: XC
Partners which are currently integrated with AAM.Best,Rachit sachdev
Hi jfumaThe issue looks specific to the Account/destination settings in
AAM for your client. Please make sure that the Advertiser id has been
shared correctly with the AAM team while creating the S2S destination.I
would recommend you to raise a ticket with the AAM support team by
writing a mail to: customercare@adobe.comThis will need more
investigation from destination from the support end.Best,Rachit Sachdev
Hi Vinodh, This is an intermittent issue due to the current design of
the Audience library UI. There are Asynchronous calls happening backend
with "Create_Trait" and "Fetch_segment_size" requests in any random
order. Fix for now is to keep trying to add filter one by one, add next
filter only when you don't see the "failed to fetch_segment_size" error
upon adding a filter to the audience. If it gives you the "failed to
fetch_segment_size" error, try again. Keep on adding filters one by one,
till...
Hi Ram,Customer attribute data once uploaded cannot be deleted unless
the data source is deleted otherwise.You can modify the schema by
uploading a new file with the changed schema but the profile/customer
id's once uploaded cannot be deleted.Looking at your questions:Question
1 : How to delete a particular record from data source ?-- This is not
possible. Customer attribute file upload either merges or updates the
given record. But delete is not possible.Question 2 : How to flush/erase
all reco...
Hi nicolar24422643You can check the number of segments shared to
Marketing cloud by viewing the People core services- Audience library in
Experience cloud.Audience library lists you down all the audiences
created in Experience cloud/Audience manager/shared from Analytics.
Hi Vijay,When you create Trait Builder rules, it is important to preface
the key variable with a recommended prefix. These prefixes identify the
type of data passed in and help avoid namespace conflicts within
Audience Manager. Generally, you can give a variable any name, but data
for a rule will not process if the key variable name does not match the
variable name in an event call.As mentioned by you,
c_events,c_evar,c_prop are customer specific data.For using Platform
related variables use the...
Hi Hiro,There is no limit to creating segments in Analytics. However,
you must limit the number of Audiences shared to Marketing
cloud(segments published to Marketing cloud) to 20 to avoid additional
processing delays.
