Oh! It looks like this is absolutely supported and is the same thing that Gigazelle was referring to. Link to documentation : pageURL I think it's super nice to think that I could use this to remove user-specific query string arguments so that URL aggregation would be cleaner / easier.

Disclaimer - This is perhaps not supported... but at any rate, you might try this:In your s.doPlugins function, add this line: s.pageURL = s.pageURL.toLowerCase();In my tests, I found that this value is the source of s.g when the beacon is composed and transmitted. Thanks for the question.  I learne...

Should be working...   Here's my test:Setting evar2, eVar3, and server via the AA extension UI (Set Variables)AA custom code : s.list1 = "ONE|UNO|EIN";var trackedVars = s.linkTrackVars.split(",");trackedVars.push("list1");s.linkTrackVars = trackedVars.join(",");_satellite.logger.log("HEY THERE!",s.l...

Agreed, there are many ways to skin a cat.  I had logged this as an issue in launch-beta a long time ago, but it didn't get any response. I logged this here as an idea since _satellite.getVar has been on the list of DTM functions that are meant to be forward compatible to Launch.  I'd expect the fun...

In the same console.log where you are verifying the value of s.list2, log out the value of s.linkTrackVars.  If you do not see "list2" in s.linkTrackVars, you'll want to add it. Here's the supporting documentation: s.linkTrackVars //example codevar trackedVars = s.linkTrackVars.split(",");trackedVar...

As long as you are counting page views on each of those pages, you can get your answer in analytics.  In your case, you have a dimension (page name) and a metric (page views).  You may be able to get your answer directly from a page names report if you can easily filter based on the text of the page...

In DTM,  _satellite.getVar will honor the "window." prefix in the first argument.In Launch, this is not supported. For example :_satellite.getVar("window.digitalData.page.pageInfo.pageName")It is fairly common practice in DTM to use the above as it will fail gracefully if any part of the nested obje...

Yeah, you're working too hard...In DTM, the onClick handler is created for you when you create an event rule. This all happens in the Conditions section of the rule: Note the event type is "Click" and the Element Tag or Selector is set to "a" indicating that I want to set up a listener for any click...

Under Extensions in Launch, you'll need to install and configure the Adobe Analytics extension (I assume that you've gotten this far). Within the extension configuration, you'll find a section named "Configure Tracker Using Custom Code".  This is the place where you will add your plug-in functions a...

Hi Justin. I'm just seeing this thread and thought that I'd add my two cents if it's not too late. 1) Debugging mobile AA calls is certainly a pain-point.  It always seems to end up getting solved with some network proxy tool, be it Charles, Fiddler, Cloud Middleman, or other 3rd party solution.  Ad...