Figures that you were working around an issue.... Particularly
interested to hear that you've noticed some issue with the JavaScript
promises... we've also noticed that it doesn't always seem to wait for
one action to complete before executing the next (even though we got
"run rule components in sequence" selected in the property), and we've
also seen some oddities where the order of rule execution doesn't seem
to be respected unless we put larger gaps between the order number (e.g.
we can't go ...
That's really interesting that you've got over 100 rules that include
the send beacon action and clearVars action. We've set up Launch so that
we've got just one rule that executes all the time to clearVars (we've
used the ordering to ensure it always happens after the beacon has been
sent), so we've only got one place we have to do this. (we've also only
got 2 rules for sending - one for s.t(), one for s.tl() ) I can
understand how this might be a frustration if you're having to manage
this in ...
clearVars is already available as part of the Adobe Analytics extension
without the need for custom code (although you do need to add an
additional action)...
You can customise the colour pallet for the project as a whole (project
> project info &settings) - As far as I'm aware, this is the only
control you have over the legend colours
Screen shot showing where you need to drop the segments in so they stack
rather than breaking down: Note: it will say "+Add" rather than
"Breakdown" if you've got it in the right place
Got it - it's where you are dropping the segment in that's causing it to
breakdown rather than go one beneath the other. Give me a min and I'll
post a screen shot
Apologies in advance if I'm missed something, but could you not just
create segments of the classification values if that is what is showing
in your screenshot?
Instead of using the dimension in your table, you can create segments
for each item (e.g. stronglyAgree) and drag them into left side of the
table and it will retain the order in which you drop them in. You may
also be able to do this directly with dimension items.
I think this should be possible. Can you describe the type of report in
Analysis Workspace you would want to create using the data as it will
determine the best approach. I'm thinking you'll need to use the
s.products variable and a merchandising event.
Description -Currently, there is no audit logs of activities undertaken
by admins available within the interface.Why is this feature important
to you -Admins have the most elevated level of access and therefore the
pose the most risk. It is important that activities undertaken by admins
are auditable both to deter against abuse and to help investigation when
things go wrong.How would you like the feature to work -An Audit log
available within Experience Cloud administration interface detailing a...
Description - One of the limitations of using the setVar() function to
create a data element rather than the Launch interface is that you have
no control over the storage duration.Please can you consider adding
control over storage duration?Why is this feature important to you -
Improved flexibilityHow would you like the feature to work -An
additional optional parameter that allows you to choose the same storage
duration as the Launch interface i.e. none, page view, session, visitor
For example:...
Description -Please add the ability to search "resource changes" in the
edit library screen. At the moment it is possible to search "resources
upstream" but not the "resource changes" which seems odd as it is the
changes you are work on and therefore most interested in 🙂Why is this
feature important to you -Improved workflow/easy of use: We often have a
lot of changes in a library. Without the search functionality it's
difficult to find things.How would you like the feature to work -Add a
searc...
DescriptionTypically, we want to compare the latest version of a
rule/element to the live version. It is very rare that we want to
compare to the previously saved version which is likely to be a minor
tweak/save point.Why is this feature important to you?This simple
enhancement would save timeHow would you like the feature to
work?Default to live revision vs. latest revision. For example, if the
current revision is 10, and the live revision is 6, default to revision
6 (live) vs. revision 10 (lat...
This would make a lot of sense, I would assume for consistency Adobe
would make it work like 'tags' in Adobe Workspace for the project list
or components. i.e. if you want to search for a 'tag' you just put a '#'
in front (e.g. #clicks #facebook #all pages)
At the moment the starting point for any new library is the 'upstream
resources'. However, we are finding situations where we want to use a
library that is in development as the starting point. The only way to
achieve this seem to be to recreate the setup of the other library by
manually selecting the same revisions - unfortunately, this is time
consuming and prone to error 😞 Please can you consider introducing an
option to 'copy' a library in development to use as the starting point
for a new ...
Classifications could be used to relabel these values
https://docs.adobe.com/content/help/en/analytics/components/classifications/c-classifications.html
That would be useful - I think the ability to add 'tags' in the same way
you can in Analysis Workspace would be good as well (possibly more
flexible than just having a favourites flag)
@philipk92120636 Happy to have a look if you DM me the URL. Also, have
you had a look in Workspace to see what the additional events are coming
through against? Is it setting the event more than once against a single
page view, or are the additional events originating from link tracking
metrics calls?
It's a shame Adobe don't offer this out of the box but you can work
around it using the technique I describe here:
https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/adobe-analytics-alerts/qaq-p/254895#9987170
This question was about hour of day, but I'm sure you can adapt it for
day of week. Hope this helps, any questions let me know
We have got ourselves into a situation where we have made many revisions
to rules/elements which we have not published and no longer intend to
publish. What is live and what is in our elements/rules are very
different and it is now very difficult to get back to a clean baseline
within rules and elements. The only way to do this is to manually revert
every changed rule/element to match the current live version - very time
consuming and prone to error. Please can you consider introducing a way
to ...
@ashokadiylil - if you are looking to pass the MCID from a mobile app to
a website, but the query string parameter is getting lost due to
redirects there is nothing that can be done from an Adobe implementation
point of view. You need to work with the people responsible for the
redirects to either remove them, or to find a way to preserve the query
string parameter to the point at which you can use it.
@ashokadiylil - if you are looking to pass the MCID from a mobile app to
a website, but the query string parameter is getting lost due to
redirects there is nothing that can be done from an Adobe implementation
point of view. You need to work with the people responsible for the
redirects to either remove them, or to find a way to preserve the query
string parameter to the point at which you can use it.
It would be great if in the context of mobile apps, Launch was able to
replace Adobe Analytics processing rules. e.g. allow server side
processing of the metrics calls, mapping context data variables to data
elements and then mapping data elements to analytics variables using
rules, ideally with the ability to execute server side JavaScript to
maximise flexibility - all through the launch interface/workflow I was
hoping the launch server side road map stuff would deliver this, but is
seems to be...
@Andrey_Osadchuk this would be really useful. Reminds me of something
similar I was trying to get across a couple of years ago...
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-platform-launch/launch-easy-auditing-of-workflow-steps/idi-p/334397
If Adobe's listening, there's at least another six likes for this idea
right there 🙂
It's great that you can get from the "edit library" screen into a
rule/element to compare revisions. However, it is frustrating that when
you close the rule/element you lose the context and get kicked out to
the element/rules list rather than back to the edit library page. How it
currently works:Edit Library > view rule > compare revision > *close*
compare revision > *close* rule > rule list page 😞 How it should
work:Edit Library > view rule > compare revision > *close* compare
revision > *clos...
When comparing revisions it is often the current live version that you
want to compare to. However, there is no easy way to see which revision
is the one that is currently published to the live environment. Please
could you consider introducing some kind of visual indicator of the
current published version in the compare revisions screen drop down
menu?
It is a while since I looked at this so I could be wrong or might even
be referring to an old version of the SDK. Caveats aside.... If you are
looking to set the MCID in a mobile app, I don't think you can directly
overwrite the MCID but you can set a custom visitor ID which takes
precedence over the MCID (the equivalent of setting s.visitorID on the
web). There is some nuances which may be relevant depending on why you
want to do it. As mentioned setting a custom visitor ID does not
overwrite t...
We discovered an issue (not a defect) with the Marketing Channels rules
which it would be great if it was sorted 🙂 2 factors are combining to
cause issues:Marketing Channels rules run on every metrics call (page
views and linking tracking)Not all properties are available on link
tracking metrics calls (e.g. pageName, URL, referring URL, query string
parameters etc.)As we have to rely on some of the properties that are
not available on a link tracking call to correctly ID a channel, we are
findi...
