I think the pain level of clearing out data in general in AAM is
sufficient to have a feature where we can delete an item and remove and
delete any associated items. BAAAM does not offer a direct solution to
this issue. Agree that its a slightly dangerous feature hence the
suggestion that this feature only be available to Admins AND/OR
additional safe guards are implemented. This would save me 10's of hours
in my current clean up project of a very large instance of AAM.
Currently deleting a segment can be a pain for a number of reasons1) A
segment cannot be deleted because it is mapped to one or more
destinations2) A segment cannot be saved if it contains traits from a
disabled third party feed to remove those destinations I would like a
single click (with a confirmation dialogue) to remove the segment
completely rather than complete a number of manual functions before I
can delete a segment.
Currently Adobe Analytics is not one of the destination options for
sending split audiences. If enabled this would allow for deeper analysis
of individual sub segment behaviour which is not possible int he
Audience Lab UI.
We have many apps and many websites, often when defining a trait it
would be more useful to start with a value than to start with knowing
the key to look at in Data Explorer search.This way I could see all the
key's across all my apps and websites that have match for a phase. This
would help me map and group concepts that reside across different keys
in different apps or sites!
This would provide a quick way to see where the trait is actively
collecting data from. It would also provide instant feedback if an
expected source was not matching the trait. So somewhere in the UI have
a breakdown like the following :-Sources CountSDK - 0 (This indicates
that the trait does not match SDK mobile app data)Web - 10,000Offline -
4,000 Analytics ReportSuites CountReportsuite A - 10,000Reportsuite B -
0 Reportsuite C - 4,000
Currently AAM - attempts to set a 3rd party cookie for mobile devices.
Most mobile devices including all iOS reject 3rd party cookies. Adobe
offer the current work arounds to this issues :- 1) Client can set their
own ID for those using mobile devices (requires authentication). For
many websites including publishers this solution does not scale. 2) Work
with a thrid party e.g Tapad or Drawbridge to establish links from your
AAM desktop traffic to mobile devices mapped in their data set and
The primary means of controlling the data modelling function is via data
sources label for traits. However this is quite inflexible when creating
multiple models that should run against different sub sets's of data
since a trait can only belong to 1 data source.