Currently, every time a change is made to an Analysis Workspace project,
whether it be dragging a new component or changing the date range, all
of the project's visualisations get updated "live".But when the project
has many visualisations, the "live" updates can cause a noticeable
slowdown in browser performance. This can hinder user productivity,
because the user needs to wait for the browser becomes responsive again
before performing another edit.Suggestion: allow the user to temporarily
@markhicken , my responses: Save temporary code every time you stop
typing for more than 1 secondYes. When coming back to the view after
unintentionally leaving, it will prompt you to restore your unsaved
codeYes. If you modify the code, save, or cancel we consider it
intentional code lock-in and throw away the old temporary saved codeYes,
correct. User actions should take precedence. Temporary code is saved
based on the current URL so it’s different for every viewYes. How long
should autosaved ...
My client wants to know how many hits have been sent to Adobe Target
during their current contract period. Is such a report available in
Target's interface? Or is it only available through Client Care?
Before the Adobe Analytics' June 2020 release, the header menus used to
be linkable, i.e. you could Ctrl/Cmd-click a menu and open it in a new
tab, or you could right click the menu to get a familiar browser context
menu with options related to links.But the June 2020 release has made
methods are not available any more. This is a drawback because it
hinders productivity. Here are some use cases:While running a report in
Steps to reproduce:Have a table with a few headers.Click a header and
drag it quickly over the other headers, in an attempt to rearrange it.I
have a screen recording of this problem but videos can't be uploaded in
this forum. Expected result:The dragged header is rearranged to the
position where you release the mouse. Actual result:The headers that
were dragged over get selected. When you release the mouse, the headers
remain as they were, instead of being rearranged. Tested in Google
Currently, Adobe Launch allows 3 kinds of hosts: Akamai, managed by
Adobe, and SFTP.For a CDN host, only Akamai and SFTP are viable options.
(For SFTP, this assumes that the CDN replicates the scripts found in
your SFTP destination.) So the only external CDN is really
Akamai.Depending on one external CDN as a host is dangerous. If
something happens at Akamai, it disables all Launch scripts hosted
there. Also, clients may not necessarily want to use Akamai for whatever
reasons.Idea: partner with ...
The UI for the date selector in Analysis Workspace has changed to result
in more whitespace. On smaller screens, that means a lot of scrolling is
needed when toggling the rolling date ranges.See this screenshot where
the bottom part got cut off, requiring scrolling.Also, given the absence
of a scrollbar, it's not immediately obvious that scrolling is
needed.FYI my screen resolution is 1440x900.
Currently, when logging into Adobe Analytics, the default landing page
is "Reports", referring to the old Reports & Analysis interface.But
given that Analysis Workspace is the go-to for reporting, the default
landing page should be "Workspace".Please change the default landing
Actually, your example IDs are bad. More likely they are like this:
ABC="123456", PQR="789012", XYZ="987654" Try this:Assuming your data
element is called "Facebook pixel ID".Then in your rule(s) where you
need to fire a Facebook pageview pixel, your actions would be like this:
First action: Core > Custom code_satellite.setVar("Facebook pixel ID",
"123456") // account ABC Second action: Facebook > Send Page View Third
action: Core > Custom code_satellite.setVar("Facebook pixel ID",
"789012") // ...
Try this: use a data element as your pixel ID.Now, in your rule, when
you need to send a hit to a specific FB pixel ID, use the Core
extension's Custom Code action to populate your data element, then add
the Facebook extension's Send Page View action.
@thebenrobb , I certainly wasn't expecting my idea to be worked on right
now. But I think it will be something that is requested for down the
road. Your suggestion for using different rules would work, of course,
but it's not so neat.
I foresee one feature request as a result of this change: Branching
Actions. This would solve the problem where you don’t want the Action
sequence to terminate just because one Action screwed up. E.g. there
could be:one branch (B1) that sets Custom Code, then fires the AA
beaconanother branch (B2) that sets Custom Code, then branches out
into:a sub-branch (B2.1) that fires a Facebook beaconanother sub-branch
(B2.2) that fires a GA beaconetc
Adobe Analytics has a built-in segment, "Visits from Mobile Devices",
defined as Visit where Mobile Device exists. AA also has a built-in
segment, "Visits from Non-Mobile Devices", defined as excluding Visit
where Mobile Device Type = "Mobile Phone" or Mobile Device Type =
"Tablet". The problem with the "Visits from Mobile Devices" segment is
that Smart TVs are also considered Mobile Devices, but not Mobile Phones
nor Tablets. This table illustrates the contradiction: This is
Could another session like this be scheduled at an APAC-friendly
time?@kimenw If you're still answering questions, could you answer this?
What is an ideal at.js timeout setting? The default is 15sec, which is
really long. The anti-flicker hiding script (for sites using Adobe
Launch) has a timeout of 3sec, which is also kinda long.
Agree with @jenn9 that auto-logout wouldn't be the ideal solution here.
Also because it still requires human intervention, which defeats the
purpose of doing something automatically. I'm thinking of something like
Medium's interface where, as you type an article, it saves the draft
periodically on its own.
Just wanted to add that I had the same problem here, and found that it's
because of how segments are applied in Fallout charts, as explained
Hopefully, Adobe will change this so that the Fallout report in AW is
consistent with its R&A cousin.
While a user is making changes to any rule or data element, autosave the
changes periodically (e.g. every minute). If the user is logged out
automatically – which erases all unsaved changes, the user can have the
option of recovering from his last auto-saved state and pick up his work
from there. The autosave does not need to create a new revision
automatically. New revisions should still be made when the user saves
@Amelia_Waliany , both Analytics' and Experience Platform Launch's "?"
Help menu have direct links to their respective documentation homepages.
And there's also no reason for documentation to be "hidden" from Help,
given that Target requires a lot of help and learning to be used
Analysis Workspace provides a built-in "Days Since Last Visit"
dimension. However, this is at a granular "day" level. In some
visualisations, it would be more useful to see this by buckets, e.g.
"same day", "less than 3 days", "less than 30 days", etc. Since this
dimension cannot be classified (using Classification Import or
Classification Rule Builder), it would be good if Adobe can create a
"Days Since Last Visit Bucketed" dimension to support visualisations
that don't need granular per-day va...
Steps to reproduce:Open the AEC homepage at
and open in a new tab --> because I want to keep AEC homepage available
to access other products.In the new tab, the browser attempts to load
result:The browser eventually reaches
https://experience.adobe.com/#/@companyname/target/activities, just as
it would if you had left-clicked Target icon in the AEC homepage. Act...
Since the internal search function at docs.adobe.com isn't working
properly, replace it with Google Custom Search. After all, Adobe's own
employees already suggest searching docs.adobe.com with Google anyway
So save your users the extra step of going to google.com. Here's a
mock-up of what your internal search could look like:
Look at this screenshot: Did you know that you can edit the schedule's
time by clicking the "2:53 PM" time? I bet you didn't. Because the "2:53
PM" black text looks just like the "Feb 11 2020" black text, just as it
looks like the black text every where else. So your first reaction was
"that is static text, not a link". Adobe, for a creative company, this
UI design is really backwards! Stop hiding user-actionable links/buttons
behind a "beautiful" design. A design fails if the user doesn't