Would be good for a plugin to automate getting Adobe Analytics data into
Google Sheets. Being the platform our business uses for our documents,
this has been widely requested by our users.
For those also wanting this functionality in Adobe Analytics I've added
to the ideas board at
https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-ideas/rolling-daily-monthly-yearly-active-user-metrics-user-stickiness/idc-p/385999
Please like and up-vote.
Retention as reported in the cohort table and the active user metrics
are two different measures. Further more trying to chart the included
column of the cohort results in each date being charted as a separate
series. Further more the cohort report doesn't include any user
stickiness metrics.
Description - We wish to be able to create a table and line chart that
contains a break-down by day which includes metrics to look back at the
unique visitors for the past 30 days and 365 days, as well as including
a user stickiness metric which will be defined as MAU/YAU. For example:
Why is this feature important to you - Active users indicate that people
are interacting with our app/website. Determining the number of active
users over time helps us with assessing the effectiveness of our
mark...
We currently have our own automatic testing bot the periodically checks
our website that specific tasks can be completed however these tests
fail when we run experiments as we only change these tests when the
winning experiment is deployed. Would love it if Adobe Target could have
an account level setting to exclude certain user agents so that
experiments are not served to them. I know this can be done at the
moment on the per activity level but being able to do this at the
account level would m...
Improve the error messaging of data warehouse reports when there's
errors.For example the current error I was provided of "Internal error.
Contact support." isn't useful to resolve myself and days later am still
awaiting a resolution to resolve the issue when it should have been a
simple task to create a data warehouse report. Change the Status
Descriptions to add additional error messages that help the user resolve
the error themselves or at least give more context would be greatly
appreciated.
What I thought was a simple task turns into something that 3 days later
are still awaiting for client care to assist with.Something that a
simple descriptive message could have solved. Also can't believe that
after 10 years this hasn't been addressed. Would not only make users of
Data Warehouse make happier to quickly solve the issue that gave the
report an error but help reduce these queries to client care. Data
Warehouse could do with a UI refresh as well to make it a bit user
friendly to use ...
Answering my own question but we came across this article that we have
guided our experiment design
on:https://www.abtasty.com/blog/ab-testing-seo/In it, it mentions:not
exclude Google’s bot from your A/B testsdo not display pages that are
too different from one another to your users. Specifically for redirect
experiments it recommends:Never block Google’s bots via your site’s
robots.txt filePlace a canonical attribute on the variant page and set
the value to the original page.Redirect visitors ...
Please make the field width for Available Report Suites and "selected
report suites" wider on the Classification - Create FTP Account screen
as our our report suite names are cut off and can't tell which one is
the staging vs production one. Example below of it being cut off:
Would be great to see the ability to specify the relevant permissions at
the Workspace custom template level to give specific users the ability
to edit that Workspace custom template.
Hi all We are looking at running an upcoming server side experiment
using Adobe Target's Node.js implementation and was wondering if it is
safe to run server-side A/B testing and what considerations should be
made? For example, we have an upcoming redesign of our internal search
result pages where we wish to use server side Target to show 50% of my
traffic the old search design, and show 50% of our traffic a completely
different search result page, are there any implications to SEO and
organic s...
Great to see more of the features we are used to in DTM make it's way
over.One suggestion however is to add the date the revision was made and
by whom. This makes it easier from an auditing perspective, especially
if there are rules yet to be published that you need to chase up with
another team member as to whether they are ready to be tested yet or
need to be disgarded.
I'm currently in the process of trying to determine when a particular
rule change was made and by who and it's currently a painful process of
going through each page in the audit logs until I find it. Very painful.
I always run into the issues with the delay link function, especially
where JavaScript is used to deliver one URL on mobile devices and a
pop-up on desktop. Usually with delay link active it will send the user
to the mobile URL instead of the light-box popup on the desktop
experience.
This would be super useful for context in Workspace reports. Would also
be great if their was a calendar events visualization table that could
be dragged in to show a list of calendar events within the workspace
panel time period.
Would be great if you could add an additional workspace table
visualisation that instead of showing dimensions nested by one each
other as breakdowns would instead show multiple dimensions as separate
flat columns on the table.For example:Dimension 1Dimension 2Dimension
3Metric 1Metric 1
In using the new Single Page App (SPA) Visual Experience Composer in a
React JS environment, there have been instances where I've made a
modification like a heading text change which has persisted past the
view on which it was defined. This is less than ideal.Would love to see
added functionality that would provide the option to clear any visual
editor changes for each of the following scenarios:user navigates away
from the view in which the Visual Experience Composer modification was
applied;us...
Currently it is extremely difficult to create a multivariate experiment
in Target using code (either JavaScript or CSS changes). Currently you
have to select a element and apply a HTML offer(s) to it.Ideally there
would be an easier to add code multivariate in the UI without the need
to select an individual element to apply it to.
Add an option to switch the reporting method to Bayesian reporting
instead of frequentist.Some of the benefits of using Bayesian over
frequentist are that it takes a shorter time to get results, results
tend to be easier to communicate to other stakeholders using this method
and helps reduce the Peeking bias issues.
