While we're at it, it would also make sense to expand the values that
you can add to custom events (for serialization) to the same 64
characters as opposed to the existing 20 characters there.
I know that this is a bit of an old post, but in case anyone searches
for this and finds this post, it's worth noting that the
_satellite.setCooke/readCooke/deleteCookie functions are not supported
in Adobe Launch. So, you will run into problems when migrating there if
you use these functions.
Problem:I see many Workspace (or standard Reports) users drilling down
from things like Marketing Channel Last Touch reports down to other
reports like "Referrers." The problem here is that the user is drilling
down from one report/var that might be Last Touch, 30 Days to another
variable that is Last Touch, Visit. This causes breakdowns that do not
make sense to the average user.As a consultant, I have answered question
as to why things like this do not make sense for more than 10 years
(i.e. t...
Scott,You need to go to the custom page code section of the Adobe
Analytics tool in DTM (in your DTM rule). There you'd set the event like
this:if(_satellite.getVar('currency_data_element')){
s.events=s.apl(s.events,"event10="_satellite.getVar('currency_data_element'),",",2);
}This assumes:You have the "apl" plug-in in placeYou have a data element
named "currency_data_element" in place that has the value that you need
to pass to the eventThe above example just sets this in the events
variable an...
No problem, Chad. More often than not when a site is transitioning, you
have valuable data on the page that you still want. In those cases, my
first recommendation is to change the vars as I mentioned. If that's too
difficult, I'd recommend changing the object in DTM to something other
than "s" while ensuring that your vars on the page still have s defined
so that they don't error out, and then set those as data elements in DTM
and assign as needed in your rules.- Jason
Paul,What you want to do is use direct call rules. So when a view
changes, you'd set something like this:_satellite.setVar({ "page
name":"[value for page name]", "site section":"[value for site
section]"});_satellite.track('angular page view')Then you can just
create a direct call rule for the condition of "angular page view" and
set the page name and channel (as an example here) in that rule.- Jason
It'd be nice if as you use the tool and discover you might want all
columns in a report (as opposed to only the drill downs), that there
would be a button that creates a data warehouse request that you can
edit and then schedule or request.
I don't know that I'd try this. Sure, you could update s.account in the
custom code of a rule, but how might that interact with other page
load/event rules that might conflict or that you want to go to diff
suites? It would likely turn into a nightmare to manage in the long-term
even if you could pull it off.
No problem, Chad. More often than not when a site is transitioning, you
have valuable data on the page that you still want. In those cases, my
first recommendation is to change the vars as I mentioned. If that's too
difficult, I'd recommend changing the object in DTM to something other
than "s" while ensuring that your vars on the page still have s defined
so that they don't error out, and then set those as data elements in DTM
and assign as needed in your rules.- Jason
Chad,Are you trying to use the "Code Exists on the Page" option with in
DTM, or are you letting DTM manage the analytics library and trying to
set vars directly on the page using s.propX in addition to what you're
in a DTM implementation?If you're migrating anyway, I'd also suggest
ditching the "s" object on the page in favor of something else that's
not specific to Adobe nomenclature. Something along the lines
of:analytics.userAccount="[cookie value]";Then setup a data element and
in fact do it...
I just do this and it works fine:[img]Screen Shot 2014-09-16 at 4.21.41
PM.png[/img]Also, if you want to see the output in the console, I'd
suggest using "_satellite.notify()" and then looking at DTM in debug
mode so that you don't have to worry about old browsers and
"console.log()."- Jason
