Hi Jignesh,Marking a trait as common or rare is what happens behind the
scene when the algorithm runs. What we get to see is the list of
influential traits after the model has run.Looking at the influential
traits list will give you a good insight on which traits are influencing
your model and perhaps bringing in more of the users as the look-alike
users.There isn't a direct relationship of accuracy with the influential
traits. So, I think reviewing the influential traits list and
accordingly se...
Hi TC,Thanks for your question and I think, you got it right.The
algorithm takes care of the commonly occurring traits in the selected
data source and these traits are ranked lower. Please check this link
for more information on the trait weight -
https://marketing.adobe.com/resources/help/en_US/aam/traitweight.htmlCheers,Kumar
Pritam
Hi Karthik,Thanks for your question. The ID Sync between AAM and a
Partner is first established by Adobe and Partner as part of AAM Partner
onboarding process. So, if an ID sync needs to be established between
AAM and Google Adx, it has to be done by Adobe and Google.As you would
see in the note section of this document - AAM Onboarding Integration
Could you please provide more details on the context and the
requirement, clarify what you want to achieve here by ID Sync, and what
is the basic use...
Hi Dave,I can provide you some information to get started on this. You
will need to do two things as listed below:1. Algorithmic/Look-alike
Modeling - It's an AAM feature that you can leverage to create
look-alike audience - Here's a link that explains what it is and how to
create the look-alike audience - Algorithmic Models2. Facebook
Destination - Create Facebook destination (URL Destination) in AAM to
send the audience (audience created via look-alike modeling and/or any
other audience/segmen...
Hi Harshit,Yes, the trait will populate when the ID sync happens on the
site if it hasn't happened already in the past. The uploaded data will
remain in the AAM and currently, there is no purging of data. Even after
a month or year, if a user does the id sync on site, the trait will be
realized.Cheers!
Hi Harshit,There will be few concepts come into picture here.1. TTL
(Time to live) for a trait - The users who are part of a trait will be
targetable (can be sent to destination) until trait's TTL (generally,
TTL for a trait is set as 120 days, you can change it based on your
needs)2. AAM UUID expiration - If the AAM UUID has not expired, the user
will be targetable (can be sent to destination). The AAM UUID doesn't
expire as long as the user is found on the web properties across AAM
customers. ...
Here's my response to your question.Hi VarunThanks for replying. See my
comments belowQuestion 1We have segments in AAM that are based on the
following profile merge rule: 'No Authentication Profile' + 'Current
Device Profile'The segments are made up of on-boarded traits from our
CRM cross device data source (no rule based traits). I would therefore
expect the population of these segments to be 0. However we see that
these segments are populated. Can you help me to understand this
please?Varun (...
Hi Harshit,As per my knowledge, the onboarding works via the FTP/S3
bucket that I described earlier.Regarding the "people" tab to onboard
file, is this feature already available in AAM or is it a feature to
come in future? I am unaware of this. Also, could you please share the
post/article on the "people" tab that you are referring to?Cheers,Kumar
Pritam
Hi Harshit,I think you are on the right track. If you have already
implemented the ID sync as per your link, you are good on the
pre-requisite for the CRM onboarding. The other ID sync link that you
have shared is another approach to do ID Sync that is file-based ID Sync
(less used compared to the ID Sync on the web properties).Here's to give
you more details and answer your question.The onboarding process
consists of 2 core components:ID synchronization (You seem to have
completed this already)...
Hi Harshi,Here's how you can validate your SSF implementation:Unlike the
client side implementation/integration, server-side integration does not
send Analytics data to demdex servers in a separate event call. Instead,
there are additional parameters in the Analytics server call, both in
the request and in the response.The additional parameters in the
Analytics call can be viewed in the Digital Pulse debugger, the network
tab of the browser or via a packet sniffer like Charles. The screenshot
be...
