Interesting! I know this will probably sound strange, but do you mind
selecting the week I chose initially (March 14-20) and repeat? I also
get good behavior if I start with the panel's date range as Oct
3-9....or even March 21-27! However, if I choose March 14-20, I
consistently get the behavior in the screenshots. Same behavior using
Incognito and across multiple reporting suites. Interestingly, if I
start with March 7-13 (the week before the time period I mentioned in
the original post) and r...
Looks like the recent changes to introduce times into the date range
selection may have impacted the Compare Time Periods feature in
Workspace when attempting to compare to the prior week. When selecting
the "Prior Week to this date range" option, the resulting time period
generated has an start date that is one day after the date range of the
panel....and an end date that is one day before the generated end date
(i.e., both dates are wrong and the compare end date occurs before the
I don't think this is correct. I have many alerts in place that are
based on calculated metrics. The issue I have, however, is the
Adobe-provided calculated metrics do not show as available options
(i.e., only custom calculated metrics are available for selection).
Given that alerts now supports calculated metrics, it would be nice if
the Adobe-provided calculated metrics (e.g. Revenue / Visits, Conversion
Rate, etc.) could be selected. Being unable to do this, I'll need to
create my own version...
At some point in the past, it became possible to create alerts that are
based on calculated metrics. However, I've noticed that the
out-of-the-box calculated metrics that Adobe provides (e.g., Revenue /
Visits, Conversion Rate, Page Views / Visits) are not available for
inclusion in an alert. Naturally, it's easy enough to create our own
custom metric that mimics the OOTB Adobe metric, but I believe these
OOTB metrics were provided so that customers wouldn't need to create
their own. Anyone know...
@josejr19- Your post helped me put the pieces together - it was a setup
issue on our end. When I looked more closely at the delivery beacons, I
realized on the page where my activity should have been triggering that
the delivery beacon was not referencing my custom mbox. We're deploying
the custom mbox via Adobe Launch and the rule for this wasn't triggering
on the page we are testing. Doh! With the mbox rule in Launch now
corrected, I'm seeing the custom mbox in the delivery beacon; to your
Thanks for your reply, @josejr19. It's an extremely simple activity in
Adobe Target: 50/50 A/B Test composed with the form-based composer and
setup with 2 experiences, both of which are exactly the same (i.e. have
the same audience refinement). Reporting is set to the appropriate Adobe
Analytics reporting suite, but nothing shows up in AA when the custom
mbox is used. However, if we switch the Activity back over to the global
mbox, then data begins to populate in AA.
I am really novice in Adobe Target, so please be gentle here! We are
looking to integrate Adobe Target on a new website and have the ability
to view results in either Target or AA (via A4T). When we use the global
mbox, all is well - no issues seeing activities/results in either area.
However, we are trying to utilize different custom mboxes per website.
We believe we have the custom mbox setup properly - worked with Adobe
consultants on setting this in Launch via a call to
I'm noticing this, as well, with some of the standard Adobe calculated
metrics. Have an existing Workspace project that had Revenue / Visits in
it, but now getting an error on that metric that says "This metric is
not enabled for this report suite". So, I create my own metric....and
then attempt to do a Compare Time Periods on it. However, the Percent
Change column now has the same message. Nice.