@garrettchung @jayakrishnaaparthasarathy Thanks for jumping in here! Me
and @Karthikeyan_Tamilmani are working in this together. Let me chime in
with some more context:1. Context: We are doing a WebSDK migration from
AppMeasurement. In AppMeasurement, when we setup SSF, there is an option
to set a first part cookie (which holds the UUID) and our client was
reading this (using Launch) and pass UUID in an eVar.2. Use Case: My
client has some AAM integrations where 3rd party ID syncs are not
Hello Folks,We have setup an AAM Source Connector (to our AEP instance)
to pull in some historical AAM segments during our migration to CDP. We
just 2-3 segments to be available in AEP. While setting up the
connector, we are selecting these 2-3 segments (size of 2M profiles).
But lot of profiles (100M+ profiles are ingested till date and it keeps
growing) are ingested in AEP which is way beyond our contracted
profiles. Still, we are not able to see the AAM segments in AEP (under
Have you tried changing the rule order for both the rules. You can do
that under "Advanced Options" when you are setting up the direct call
rule event configuration. The lower value rule gets fired first.
@umamaheswariy46 This is not available ootb. But this is possible. You
should be using APIs for this. Here is the API documentation for getting
the Data elements -
can use it in excel (VBA scripts to list down all the data elements and
rules) if you want to analyze and optimize and take action. I have seen
this approach working better than listing them in a simple web page
(using HTML and JS which is an easier option, bu...
Can you clarify where you are creating the segment? In AEP or AA? In
AEP, the segment numbers are "profile count" which is an estimate and
depends on the unified profiles. So you cannot compare the UVs from AA.
If you are creating segments in AA, then the bulls eye chart represents
the qualifications for a different period of time. So you need to select
the right date range in the reports. Still your reports might include
current data, where the numbers will be a little off.If your question is
The advantages depend on your licenses as well. Lets say you have only
RT-CDP license, then CJA will not be there for data analysis. In this
scenario couple of major disadvantages are:1. There is no marketer
friendly way to look at the data to create segments (only thru Query
Services)2. There are many ootb processing that AA does, for ex: like
marketing channels, hit depth etc which will not be available in AEP.
These needs to be done again using Query Services using the data
collected.So if yo...
@Ankita_Sodhi Thanks, helps! I was trying this with my sandbox and was
not able to find the AAM datasources (cross-device) listed in AEP's
Namespaces. Should we require provisioning for this? We already raised a
provisioning for segment sharing b/w AEP and AAM, is this related to
@jayakrishnaaparthasarathy The "datastreams" is a configured instance of
Edge Network, which is the data collection endpoint (new and futuristic)
for all Adobe solutions. Even if your client is not using this
configuration ( I am not sure how, I guess they are not using Launch or
some other direct method of implementation), they would still be using
the edge network for data collection, as defined by "Edge domain "
configuration in Web SDK. This would give the edge segmentation features