Hi, We've a audience segment from a 2nd party (say X) in our AAM
Instance (say Y). This was done via Adobe Marketplace. 2nd party, X is
also on AAM and they pushed the segment via Adobe marketplace to our
AAM. We do have the segments populate in our AAM instance. We have
mapped this segment (from 2nd party X) to our Adobe Ad Cloud (AMO) and
to Google Ad words as a URL destination. We've mapped another segment to
Google Ad words - this segment is our audience (Y audience) and not 2nd
party. This ...
In this case it can get tricky. If you know that your user opts in and
opts out that frequently, then probably the best way to go about it
would be to upload a batch file of updated list of users. Frequency of
the batch file upload can be set to daily.
Thinking out loud, how about creating another trait (say Trait 2) for
users who have withdrawn consent - if we're capturing that action
online. Then a segment can be created for: Users gives consent Trait AND
NOTTrait 2 (users who withdrew consent)
Hi, How do we go about sharing onboarded traits via AAM Marketplace? I
know there's the AAM help documentation, but it doesn't list down the
exact steps to create a data source for a data feed for different
scenarios. Scenario: We need to share only some of our CRM traits and
not the entire CRM traits in the CRM data source say Data Source 1. So
we'll be creating a separate data source say Data Source 2 and build
just those traits that we want to share n that data source. (not sure if
this is ev...
Hi, Not quite sure if I understand the first question, but can provide
some input on the second one. The way we've used it in one the cases was
something like: Say for example, you've an online streaming website like
Netflix. There's one account and then there are multiple profiles within
it. In that case, you'd most likely have an account ID associated with
the account and profile IDs associated with each profiles. So there'll
be two cross device data sources, on at account id level and the oth...
Hi Nidhi, Previously we were able to push AAM segments to Facebook via
URl destination set up.With the recent Facebook policy changes, my
understanding is that we cannot. Facebook treats it as a third party.
Here's what I did and it worked. Created a cross device data source
based on customer IDCreated an on boarded trait with ic == "" Krux mapped the segment to their AAM destination created
based on the AAM data source IDTraits started populating within ~48
hoursThe idea was, AAM treats Krux Ids as customer ids like any other
batch file upload.
Thanks Harish ! Does the type of data source need to be just cross
device & ID type "Customer ID"? The krux data that I'm trying to ingest
does not have much authenticated users. So is it OK to create a cookie
based data source to ingest the data?
Hi, How do we go about mapping segments from Krux to AAM. I understand
that a S2S destination can be set up in Krux to map the segments. But is
that how we ingest data from Krux to AAM: from S2S destination in krux
to a cookie based data source in AAM? ThanksSurbhi