Question: Because we cannot go back in time to put "New" or "Returning"
in our Digital Data Layer User Object
(digitalData.user[0].profile[0].profileInfo.returningStatus) for capture
in a variable, is there any other way identify "New/Return" users for
individual applications* within a global report suite?Background: A more
complete definition of "First Time Visit" is something like "Visit
Number = 1 for the Visitor in this report suite".This presents a problem
when you collect data from many ap...
Administrators for users at their company need to be able to use the
Marketing Cloud Admin Console to assign the Landing Page for users. We
should not need to instruct our users (and users should not need to
remember) to click the totally non-intuitive '9 dots' icon in the upper
right menu, then click on a product icon to access it.If Adobe is
requiring customers to migrate all of our users from each product level
authentication (e.g. our legacy Adobe Analytics IdP SSO login method) to
Adobe Mar...
I agree. A calculated metric for [selected number of days] dynamically
populated with the number of days in the date range of a report or
dashboard reportlet. I would like to have two dashboard reportlets
containing calcuated metrics for "Average Daily Revenue", "Average Daily
Orders", "Average Daily Visits", etc. One for the current timeframe
(e.g. this week, this month), and one with my reference timeframe (e.g.
last week, last month, this year) This was also requested in these
posts: https://...
Wrap the header and show less rows. I can always make the reportlet
taller if I need using the 'legacy' dashboards with greater height
flexibility. (On an aside, the I think the dashboard types should be
more accurately named 'print dashboard' and 'online dashboard' rather
than 'new' and 'legacy'.) At least that gives me options, rather than
forcing me into one I can't change. I can often rename my metrics with
shorter names if they are wrapping excessively.
I think this works great, and I was wrong, n/a is not at the bottom. (I
should have pulled my report rather than recall from memory.) Here's an
example screenshot where I've broken down my 'All' category by the
product lines I've uploaded in the table above. You can see calculated
total metrics, average metrics and conversion metrics all display
correctly at the top.
Step 1: Add an "All _____" Classification to your SAINT table. Step 2:
Upload your SAINT table with the same value in your "All" column for all
rows. Step 3: View your "All ___" report with your calculated metrics.
Step 4: Click the Green icon to the left of "All" and break the report
down by another to see the totals displayed at the top for that report.
(Note: It will still say n/a in the totals fields at the bottom of the
report.
Yeah, I saw that, but this isn't the same thing. I'm referring to a side
effect of sticking a report into a dashboard reportlet. The metric
columns wrap the text correctly in the report itself, but they don't
wrap and are cut off when put into the reportlet.
Admin visibility to all dashboards and bookmarks as well as the ability
to make changes regardless of the creator or their shared status is
crucial. I've encountered problems recently where I created a calculated
'Gross Revenue' metric to replace the default 'Revenue' metric. I sent
an email with instructions, but many of my users don't take the time or
are not savvy enough to fix their own dashboards and reports. Norm's
idea is great for many things, but for this it only works reactively
(e.g. ...
Yes. More and more, monitoring services are incorporating global user
emulation from a bunch of IP's. My point is that as this has become more
commonplace, I feel it's more challenging for Omniture justify only 5
IP's with a Vista or DB Vista rule as an extra add on.
What's frustrating is calculated metrics will total IF you are breaking
down one report by another:And as a bonus, this totals at the top of the
page, which is great if you stick a long report into a reportlet.As a
temporary soluion, I have created a column in various SAINT tables that
contain the same value for all rows, then break down a report by that
item. It will total calculated metrics AND put them at the top of the
report.
Here's how it looks in the reportlet:And here's how it should
look:ADMIN'S NOTE: See the comment from benjamingaines on page 2. We
need some feedback about possible solutions to this problem!
