Hi @manojk62306941 We did have a few extra settings on the AAM Data
sources, do you know if any of these settings could have caused it to
fail?"Share Enabled""Share associated visitor or devices across the
Audience Manager Platform""share associated cross-device IDs in people
based destinations" settings could have caused this to fail?I just
removed these settings so we'll see if it helps, Thanks a lot for the
response and your help!
Thanks, @Milan_Vucetic We can see the IMSorgId in the tracking servers,
and had the outbound setting enabled, but we did have a few extra
settings on the AAM Data sources, do you know if any of these settings
could have caused it to fail?"Share Enabled"Share associated visitor or
devices across the Audience Manager Platform""share associated
cross-device IDs in people based destinations" settings could have
caused this to fail? I just removed these settings so we'll see if it
helps, Thanks a lot...
Hi, We're using Campaign Classic, and have been working through the
integration to pull segments from AAM. We've completed setup by
following this guide and have had Adobe set up the necessary provisions:
we reach step 10 in the guide above, and click "Select a shared
audiences", a new window opens as expected; however, that window never
loads any of the Shared Audiences we have created from AAM, please see
screenshot below: ...
Hi all, Two questions today: I'm curious if creating a cookie
destination increases the number of server activities we're being
charged for? We have one created to help QA segment qualifications, but
our "Others" server call type category is running fairly high, as is the
Target type.Is there any way to reduce the number of times the Target
server call type can be reduced? We are utilizing the server side
integration via the ID service, and have Adobe Analytics with server
side forwarding to AAM...
More of an assumption than an exact answer since I don't work for Adobe,
but I'd assume it's still a blend of probabilistic and deterministic. I
say that because the UUID is persistent for each device across all AAM
client domains, so even though there may not be an authentication event
on your website, it might be linked elsewhere.
Thanks, Shweta, So there's no way to tell how many users are in an
onboarded trait in between file posting intervals? Assume I post a file
one a once, that's a fairly long time to wait and seems to be a large
gap in the product.
Hello team,Hoping someone could help me understand why our onboarded
trait metrics do not seem to change.Setup overview:An ID sync with CRM
ID is occurring when authenticating onsite into a global data source.
Traits are set with a target data source. We have multiple inbound
files, target data source used to avoid unwanted overwrites.When viewing
the device ID settings, our unique trait realizations & total trait
populations never change. My assumption was these would scale over time
You'll have to create a new segment, the segment rule would look similar
to this:(Visitors of page A trait OR Visitors of page B trait) AND NOT
(Buyers of product A trait OR Product B trait)Otherwise you could
combine Segment 1 & 2 in the destination itself.
Hi ASodhi-AAM -Thanks for the response, and sorry for my delayed
reply..There is no 3rd party data in this use case, so I don't
understand why there is a 3rd party ID sync dependency? This segment
share is just to Adobe Target, which utilizes the ECID. We are targeting
profiles when they have authenticated; however, the customer's
authentication state is not included in the ID sync. So I'm also
confused on how the last authenticated profile PMR would even function.
You'll have to request a few exports from customer care:1- your ID sync
export, this will provide your declared ID (CRM ID) to a UUID2 - a
segment export, this will contain all the UUIDs in your segment, map
against #1 to get customer data backOr3 - request a CDF log to be
created to collect event level data (will be very large overtime best
for data lake environments)Hope that helps, all will be available via an
Hello,Curious what the recommended profile merge rule configuration is
in order to share a segment comprised of only on-boarded traits to a
server to server destination? Would this change if we wanted to deliver
the segment to Adobe Target via the ID service/people core services?All
the traits are ingested into AAM via Natural Match, which is keyed off a
customer ID, and we have an id sync for that customer ID on
authentication onsite. Additionally, we are not passing the
authentication state in...
Hello,I'm trying to figure out how to implement an ID sync when
customers open/login to my company's mobile app. We have AAM, Adobe
Analytics (SSF enabled), and are using Adobe Mobile Services (AAM SSF
enabled), but I can't quite figure out when/how to implement the ID
sync. Can anyone help please, seeking advice for both iOS &
hello!hoping to receive some clarity around the differences of using
adobe analytics server side forwarding (SSF) to send data into AAM
compared to just using the DIL code. Specifically from an ingestion /
time proceasing stand point. If I implement SSF will my analytics
information reach the AAM servers faster than if I were to use DIL? main
point of consideration is performing same page personalization.
Solutions in use for this scenario are adobe analytics, AAM, target and
the ID service enab...
Hi,Newer to Ad Cloud, and I'm curious about it's integrations with Adobe
Analytics and then ultimately Adobe Audience Manager. Is Ad Cloud able
to pass display media exposure back to AA, and then have this forwarded
via Server side forwarding to AAM?If there's a write up on the benefits
of using AA + AAM + Ad Cloud that would be wonderful too.Thanks all!
Thanks Christophe_Jossic. Yes, I've reviewed these; however, they don't
actually indicate what will be captured by DIL. For example, will any
custom events I've created in GA be passed to AAM. Any additional
details would be helpful.
Hello,Hoping to receive some clarity on what specific Google Analytics
elements can be captured in AAM? I could only find documentation around
how to connect the two, no details around what elements will be received