Processing Rules are pretty powerful (at least have ability to destroy
our data) and therefore there was a point in time when those were only
allowed for admins with a specific certification.But since then the UI
didn't improve much (I think that just the original limit of 50 rule
sets per Reporting Suite was increased and extra condition with a rule
action was added).But we still have major issues with using Processing
Rules - namely:the UI is cluttered and slowthere is no way to properly
debug...
An this somehow not very obvious message when we did everything
according to the docs is in the same area of being ok?09-10 14:12:50.402
1260 1496 E AdobeExperienceSDK: EventHub(AMSEventHub) - Circular
shared-state dependency between com.adobe.module.analytics and
com.adobe.module.identity, you may have a live-lock.
I have the same issue here:09-10 11:19:01.489 7271 7327 E
AdobeExperienceSDK: AnalyticsExtension - Couldn't retrieve shared state
for com.adobe.module.configuration. Please make sure you have registered
and configured the com.adobe.module.configuration extension properly
based on the documentation.We double-checked everything with our Android
developer - everything looks like in the docs (modules are imported,
registered, configured in Launch, app is initialized via bundled file
and lifecycleSta...
ECID delays Actions (Set Variables, Send Beacon) of my Rules causing
race-conditions and unexpected behavior (Set Variables Action of one
Rule overwriting variables of another one). I can provide live
demo/details.
I totally agree with Stewart.At the moment we are trying to get rid of
Plugins (heavily inspired by the series from Jan Exner:
https://webanalyticsfordevelopers.com/2018/07/31/with-launch-you-dont-need-doplugins-part-4/
...etc.).There is a couple of use cases where I still consider doPlugins
pretty useful:adding extra logic/variables to Download/Exit links (this
should be also somehow re-built into Launch Extension, so these signals
are available to other tools as well)setting some default varia...
Hello, a couple of times I was able to get into weird situation:I was
not able to publish changes to Development Environment with Akamai
Adapter (the resulting file linked to an empty file)That was even in the
situation when I had a working file published in Production (containing
previous changes in two libraries)I tried numerous things:I deleted the
library that was not being published and created a new one (and played
with selecting it as a "Working library")I tried to select all the
changes ...
At the moment we are trying to use Reporting API for our custom-designed
LCD Dashboard in the office.The issues we have at the moment
are:Real-Time data is very limited in terms of providing consumable
information (i.e. we only have hits, but not something like Active
Users/Devices - we cannot do such calculations ourselves, because the
API is limited in cardinality - meaning that we have many concurrent
unique devices).As we are Analytics Standard client, we cannot use Live
Streams and that wou...
Wel, This doesn't help.We have Customer Attributes provisioned and
configured.The issue is, that there should be an option to define Target
Audience based on a Customer Attribute and there is none.
Hello Harsh,Your answer is probably precize, but it doesn't satisfy me.
Why should I bypass DTM in this case - maybe I would like to use DTM to
fire multiple tags around this specific event and this would lead to the
old days without TMS - I would have to do the implementation twice.😞
Hello,We are trying to implement Custom Event Tracking in Adobe Dynamic
Tag Manager, but I haven't found a way to use all parameters of s.tl()
call.s.tl(DELAY, TYPE, LABEL, OVERRIDES, CALLBACK);In our case we need
to use CALLBACK parameter to allow tracking on important links that
should perform the default action (load new page). We would like to
avoid DELAY parameter to keep the best possible User Experience (speed
in this case).Is there other way than to use a completely custom
solution in Ja...
It depends on what do you mean by DTM libraries.If you mean the main DTM
library file referenced from the Header Code, than the answer above is
IMHO pointing you in the right direction.If you mean the libraries of
various Tools that you can deploy via DTM than the answer would be
this:There are some (like Marketing Cloud Visitor ID Service or Target)
that you really should implement synchronously, because otherwise you
could easily break some of the logic.On the other hand I don't know why
Adobe...
Our internal Security Policy doesn't allow us to use any other
deployment option than Library Download.But the only working setup for
this is to include the absolute path to the library location somewhere
on our
infrastructure.[img]DTM_library_download.png[/img]i.e.domain.sk/prodBut
at the same time we need to test the integrity and performance of the
whole application in our non-production environments that are in a
remote location with no access to the public internet and run on
different host...
Since there is 1000 Success Events available in Analytics Standard the
Configuration page became totally unusable because of the complex table
of form fields loading too long.Please, please, please, break-down this
configuration into multiple pages so it loads in reasonable time.
Processing rules look uniform right now and when there is more of these,
it is hard to find the right one to edit (would be even harder when the
50-rules-limit increses in the future).We could use Rules Categories
with filtering + color coding in the Admin Console, so the reason for
particular rule is more obvious for the first sight (Adjust Data, Add
Event, Create Segment, Process Context Data Variables).
One more scenario. I have reports for multiple Success Events broken
down by an eVar (Segments) with few values (4). I wanted to have Stacked
Area charts of a dashboard, where the same values from an eVar
(Segment-1 .. Segment-4) would have the same colors on every chart. But
if there is no value for Segment-1 when displaying one of those Success
Events, I have to show the chart with different colors.
Currently, the only way to get this information is through Client Care.
We are trying to maintain the documentation, but sometimes it is hard to
keep it up to date (When we decide to use a list prop we document it as
a list prop, but do we know if we already did send the request to client
care? Did client care already make the change?). Contextual link to a
help article with all the consequences (no correlations/UVs) would be
handy.
