This idea hasn't been updated in a while, but I thought I'd let you know
we are actively working on a cross-device stitching capability that is
far more robust than using s.visitorID. It is feature that leverages an
integration between Adobe Analytics and the device graph (Co-op or
private graph.)To that end, I wanted to ask a follow up question. Do you
store a hashed user id in a prop or eVar? In particular, do you store an
ID in a prop or eVar once the user is known (via login or other means.)...
Justin/Ben - I hope this is still on the roadmap, whilst recent update
allows for row count of selected dimension report, it's not ideal/great
... eg. by site show no. of unique article counts along with a
percentage that did not specify author1. For this to work specific
dimension report along with a standard metric has to be selected ie.
having to request data (aritcleids, and standard metric) that aren't to
be used/shown2. Can't correlate ie. in this instance we'd want articleid
(dimesion) co...
This option should be configurable to minimally enable/disable per
report suite. We have a global report suite where pageName applies to
multiple domains and have users thinking that the page is just for the
one domain showing, which is causing more questions than serving useful.
We want to disable this, minimally for the global report suite and have
not been told it's possible to do.
Agreed with all the comments above. We ran into the same allocation
issue trying to track the internal campaigns and their click-throughs.
And were very frustrated to findout about the full allocation of s.lists
variables. Even more frustrating - none of the Customer Care reps
pointed that out when we wondered why all list values are getting
click-event allocations. We ended up using s.products instead - which is
not the proper way of tracking internal campaigns and won't a good fit
for everyone...
I'd love to see this happen. There are two aspects to this, and Mike
really hits on a big one (which I think Web_Analyst is referring to,
too):Actually centrally maintaining the solution design; this would be
useful for the implementation analysts and IT and, potentially, could
even be used by a tag auditing solution that would crawl the site and
validate tag completeness.The *business user* potential, to me, is an
even bigger deal. It makes me a little ill every time I groan because a
client ha...
adamhaining: what worse is that the Admin/ReportSuite API is supposed to
allow you to create/edit classifications for variables, but it is
bugged. Basically it works for editing exisiting columns, but not
removing or adding. So I couldn't even use the API as a full workaround
for bulk rsid maintenance of SAINT classifications; all I can use it for
is getting a list of the classifications and then manually change the
offenders through the web interface (I have submitted the API bug to
ClientCare ...
also sometimes it shows up cutoff. Dunno if it is because of position on
page or with certain browsers (I've seen it in FF and Chrome). I have to
click save again in order for the popup to fully appear.
I agree with the other posters here.. we work with several clients that
are quite large. Hundreds of report suites dedicated to specific sites,
markets, countries, regions, etc. Keeping things consistent all the way
up to the global rollup is a daunting task. A lot of it boils down to
red tape. Lots of stakeholders with their knife in the pie. Quite often
you end up having to burn an eVar one one little thing on one site out
of hundreds, and that has to bubble up all the way to the global rollup...
This is one of those things that sounds like a good idea on paper but in
reality, may cause more harm than good. I would not recommend allowing
new code to be introduced directly to production environments, and
allowing for updates to core code to be automatic will do just that.
I agree with what Ben said, have it something that Adobe Analytics does
by default, therefore removing the need to do it with the code. It could
even be done better where it will count it the same across all devices
where the visitorID variable is implemented.
Occassionally data will be sent in where there is a space on the end, a
tab somewhere in the value, or even a newline character. This causes a
value to appear normal in SiteCatalyst when in reality it is not. If it
were consistent, it would be fine, but sometimes it is a matter of how a
browser interprets and encodes data. This then causes 2 lines to appear
in SiteCatalyst that appear the same. To find this out I have to export
as a CSV and then open in a text editor to find the problem. My requ...
For the marketing channels it would be great to see a cross visit
pathing report to see which marketing channels users use and in which
order. It's great to have first and last touch, but the multi-touch
would be even better. I know this is possible with JavaScript
(specifically the crossVisitParticipation and channelManager), but it
would be so much more effective to easily update via the web interface,
not have to manage both the logic in the admin and the JavaScript code
I've recently come to learn that when building a page view segment on an
eVar that persists longer than a page view will include not only the
instances where the eVar was set on the page, but also all page where
the eVar persisted. I can see an argument for both sides, but I would
like to see another option in building the segment where we can either
select the peristent eVar (current functionality) or just instances of
the eVar. This would make the creation of these segments much more
intuitive...
At least there is a workaround with the ~empty~ value. The bigger
problem is if you are submitting a value of "0". This will be regarded
as "NULL" instead of "0".
This one is huge. The main reason I'd say is that the current settings
for the search keywords are rather lacking. Putting this in an eVar will
open up many more options. It'd be nice to not have to do a hack to get
this by using a processing rule (make the variable that captures this
just like an eVar by default), or by using a VISTA rule or some
JavaScript.
I can see why this would be something difficult to do, especially if it
were to show the pathing of grouped items. So maybe there can be a new
classification for traffic variables, and the requirement is that the
classifications will not be grouped, but simply a way to rename the key.
Even if the classification has the same name between 2 items, it would
not combine them in the pathing report, but simply show something like:
Page 1 > Page 1 The reason for this is to show pathing of friendly
name...
One of the settings of an eVar is the expiration. You can set the
expiration to an event, and then set that event to manually expire the
eVar. Are you wanting to have the eVar expire after a visit by default,
but then have an extra flag or variable you can set to expire it without
having to use an event? I think this would be great, since there may be
multiple scenarios where you would want to expire an eVar, and not just
after a visit.
Agreed. Maybe even some sort of regex functionality (regular expresions
make things really nice and quick to reformat). Lots of great ideas are
floating around I'm sure.
This would be a HUGE help for troubleshooting and auditing since Data
Warehouse can utilize segments. Data Feeds are sometimes too much to
handle when you want to slice and dice data, especially when having to
do event lookups. Although storing it in a prop and/or eVar isn't
difficult, it typically isn't setup when you need this and doing
historical reporting on the page URL is nearly impossible.
I'm working on a solution to track videos on the Roku device. I've got
an idea on how to do this, but wanted to know if anyone has done it and
what they did. Also, wanted to see if anyone from Adobe Product
Management had a library for this in the works.
Currently if you set Media.trackVars in a video, it will only send data
for the first server call from the video, when it starts playing. Any
additional calls, such as with the milestones or X number of seconds,
will not have the data outlined in the Media.trackVars sent with it. My
request is that all variables specified in Media.trackVars and
Media.trackEvents are sent with every media request without having to do
this using Media.monitor. This would not only make sense, but make
implementing ...
When requesting a data feed column headers are not offered. It's really
inconvenient and difficult to deal with large data feed files and no
column headers. It would be nice if this were an option when creating a
data feed, that way I know quickly and easily which data is in which
column. I know Client Care can tell me what this is, but I'd rather have
it in the file.
Building on this, as Admins have a perfectly good and easy way to build
a segment in SC v15, why not just add the ability to create segments
from within reports pages as a permission to the user management
console? That way, you could add the permissions to allow a user to
build segments without needing to change them to an admin (which is
usually an unreasonable thingt to do)
I generally don't like to use the Idea Exchange to suggest workarounds
(I don't want to give you the impression that we'd discount this idea
because there is a workaround) but one way to get this is to implement a
custom event and have ClientCare set it to serialize using the "Once per
Visit" setting. If you pull in that custom event using the first-touch
variation, it should give you what you need. . . unless I've missed
something.
