I have been toying with the idea of either rewriting internal CMS
navigation parameters or adding custom internal campaign parameters to
links to differentiate them on a page and therefore save on async server
calls (s.tl calls).Not sure how I might go about doing this, but I was
thinking of using data elements from the page and constructing new
internal campaign parameter values. Has anyone done this? Any advice?
I'm not liking that solution. I'm attempting to do the same thing.
Ideally, you should be able to just add this to your custom
code:s=window.s; s.linkTrackVars="products";That should include the
products string in the s.tl call, when your EBR is triggered. Apparently
that doesn't work either, although it should work in a normal HTML/JS
implementation.I'm going to cave and try your solution, but I won't like
i8sand wrote... salomePB wrote...
s.products=_satellite.getVar('dataElementName'); I am using the
s.products variable in an Event Based Rule. When a user clicks on a
particular link, the rule grabs the values of multiple html data
attributes and assigns them to eVars and props. In the custom script box
within the Adobe Analytics section, I have been unsuccessful in writing
a script that inserts the values from two (2) of the data-attributes
into the s.products variable. Here's what I've written:...
Is the idea that you should place this code into a page load rule only
for pages that contain products? Or would you just set this globally in
the default page load rule and check to ensure the variable is not
null?Would you then create custom page load rules for each step in the
funnel in order to set merchandising events and/or custom incrementers
and eVars? Or again rely on custom page code that checks for null
variables and handles the product string accordingly?