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
targe...
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.
We often find that users want more than one individual to be able to
edit a shared dashboard we can work around this by using shared accounts
but that's not ideal. So why not put a Google Docs like approach to
permissioning. Public / Private Dashboards (We have this now in
Omni)Dashboard Roles (Admin, Contributer, Viewer etc)I think publishing
lists could improve perhaps move to a google groups modelA group has
settings between invite only, openThat way a user can simply subscribe
to the correct...
We have a large number of daily dashboards. We get frequent delivery
problems. We also sometimes get blank dashboards and on a couple of
occasions our users have recieved a dashboard withe the correct title
but content from another dashboard. Particularly sensitive for us since
this is the method we communicate how many page views certain authors
are generating which relates to how they are paid in some cases
3 list vars are not very many when you are trying to maintain standards
across 30+ unique websites and have it all roll up nicely in to a global
report suite.
We cannot associate LifeCycle metrics with standard vars and props that
are important for use in a roll up secondary report suite. We use vars
for brand and app name rollups in the secondary report suite but some
LifeCycle metrics are not associated with these vars this creates a
large bucket of metrics that are not associated with the brand or app
name in the secondary report suite making meaningfull roll up views of
this data impossible.
In a large organisation with a secondary report suite the low traffic
bucket has far reaching implications for data integriy. For example a
primary report suite may not ever hit the low traffic limit and as such
is able to accurately report on items such as url's and page names.
However when you go to the secondary report suite which has many more
values from other primary report suites we commonly find that items are
bundled int he low traffic bucket. This creates significant reporting
descepan...
Adobe have been kind enough to give us lots of variables and events but
if you use a lot you are likely to hit character limits for some
browsers which in turn causes data collection issues. Using "Post" would
increase the max limit of characters in a send well over the current
limitation of 2083.
When I compare dates on multiple metrics the format of the table goes
very wrong. Totals align to the wrong column's and the whole thing is
rather hard to digest. Would be great if you could do some or all of the
following :- 1) Fix the inherent formating issues with a multi metric
compare date function :-2) When adding a compare date reportlet to a
dashboard allow users to select which columns they want to show. E.g
it's common that we want to hide perhaps the total under change and just
show t...
I don't know much about your set-up here but I guess a single visit can
be both in a logged out state and a logged in state. So my single visit
where I start in a logged out state but then login on the site looks
like this :- eVar login status - No = 1 visiteVar login status - Yes = 1
visit Total Visits in Omniture = 1 visit (it's dedupe since it's 1 visit
with two different logged in statuses)Total Visits in Excel = 2 (excel
can't dedupe the visit) So don't add visits/uniques up outside of
Omni...
The latest version of the s_code will attempt to set a 3rd party cookie
(if your implementation is 3rd party), if it can't set a 3rd party
cookie it will set a first party cookie. There's no syncing of 1st party
cookies across domains since this would break the privacy intention
around anyone/browser who disables 3rd party cookies. So you have a kind
of hybrid approach. Obviously as more browser block 3rd party cookies
your solution moves closer percentage wise to a 1st party cookie
implementato...
I would like to upload multiple values in a single classifcation for
example if I configure a company classification I would like to load 3
different companies into that classification per key. This would have
the same effect as if I had populated a list var or list prop using on
page tracking only this works via the SAINT import. I have many use
cases where our preference is to import this data via SAINT but we can't
due to it's inability to deal elegantly with single classificaitons that
have ...
Client Care state anything below 72hrs is normal. The problem is that
due to the unpredictable nature of the turn around it's hard for users
to trust the data reports when they could be 1 - 72hrs out of date when
looking at classification data.
Event serialisation is often the answer to a business requirement
however I find more often than not the 20 character limit prevents me
from usinging this feature. My most common requirement is to fire an
event once per visit per some kind of unique content id. More often than
not combining a visit id and content id results in a serial longer than
20 characters
With V15 page views, visits and uniques are available on all evar
reports. However if I create a simple page view / visits calculated
metric in the admin tools for a report suite it will not appear as an
option in the calculated metric selector. Yet if I create the same
calculated metric directly in the metric selector for an evar report it
works. I contacted clientcare and they say this is working as designed.
Whilst I accept this is as designed in v14 I find it hard to believe
that this is an ...
If I point users to the various mobile apps for viewing dashboards a
common complaint is that the app does not use the same formating for
certain reportlets e.g tables etc. This means that some reportlets have
diminished effectiveness at conveying insights to users and can cause
confusion. It would be great if the dashboard engine work flawlessly
across multiple devices and native apps. Plenty of data vendors are
achieving this via standard opensource tech so this should be achievable
for Adobe.
