Activity Map Page Report now showing URLs (Used to be page name)

[patrickb8312284]

Had a weird issue just come up where the page name's are no longer being captured in the Activity Map Page Report, just the URL.

I did publish a change in DTM at this time, but the only change was an addition of a production report suite in the Adobe Analytics tool, there were literally no settings or code changes published from DTM at that specific time. The change must be related to the DTM change, but it shouldn't be due to the GUI report suite change.

Has anyone else come across this?

[jantzen_b]

If nothing has changed for your DTM rule aside from the report suite, the issue is likely within Analytics itself. Have you verified that the new report suite has Activity Map enabled? Check out this entire article, especially step 2 & 3.

Enabling Activity Map

If this isn't the solution, would it be possible for you can share the URL where we can take a look at the implementation? If the beacon is firing and contains the activity map data, we know the issue isn't on the the front end and thus not an issue with DTM. If the beacon is not firing or does not contain the activity map data, we may have an issue within DTM.

[Hote097]

On further investigation we found that Activity Map function is being called twice, the first time the below Activity Map variable gets set to the Page Name. However for the second execution it gets set with the URL. Could you please assist with why Activity Map function could be getting called twice? There is no duplication for any other method.

This is between AEM 6.3 and Analytics.

[jantzen_b]

How is your activity map code being deployed to the site? I assume DTM since your original post talked about DTM and changing the report suite? If so, can you enable debugger mode for DTM so you can see which rules are firing. You'll want to check each of the rules along with the Analytics tool to see if you have the activity map code deployed twice.

If you're using AEM, you may also want to see if the activity map code is being placed on the page by something within DTM. An easy test would be to disable the DTM code locally on the machine using something like Charles proxy. This would prevent DTM from loading and tell us if anything is coming from AEM directly.

[Hote097]

Yes, Activity Map Module deployed through DTM. AppMeasurement code was customized to the needs, so there maybe a chance for an extra call. We will let you know after following your steps for debugging -

Thanks Jantzen.

[Hote097]

Hello Jantzen,

This looks like a product bug. I have seen this behavior in my local with AEM 6.4 integrated with Analytics through DTM. No customization to appMeasurement code.

Also, some of the websites I found online which are using activity map are having similar problems. Please see screenshots below -

Also,

Any thoughts on this?

Thanks,

Suresh

[jantzen_b]

Gigazelle​ - Any inputs here? You're a bit more familiar with Activity Map

[Gigazelle]

First thing I'd check is to make sure you're on the latest AppMeasurement library version. Second thing I'd check is the pageName variable value, as Activity map should be pulling from that value and putting it in the context data variable.

If you're not on the latest version of AppMeasurement and/or are using customized AppMeasurement code, troubleshooting this is going to be extremely difficult.

[Hote097]

Thanks to both of you.

Definitely, not the latest version is in current use.

Code has been customized.

Other sites mentioned above are using even older versions of appmeasurement code. Is changing to new version, solve the problem? or further debugging need to be done to see where the second call to activity map is firing.

Thanks.

[Hote097 · Accepted solution]

Following code changes to ActivityMap module fixed the problem -

Before:

e._g = function() {

        var a, d, b, c = f.contextData,

            e = f.linkObject;

       (a = f.pageName || f.pageURL) && (d = r(e, "link", f.linkName)) && (b = r(e, "region")) && (c["a.activitymap.page"] = a.substring(0,

            255), c["a.activitymap.link"] = 128 < d.length ? d.substring(0, 128) : d, c["a.activitymap.region"] = 127 < b.length ? b.substring(0, 127) : b, c["a.activitymap.pageIDType"] = f.pageName ? 1 : 0)

    };

After:

e._g = function() {

        var a, d, b, c = f.contextData,

            e = f.linkObject;

        (a = f.pageName) && (d = r(e, "link", f.linkName)) && (b = r(e, "region")) && (c["a.activitymap.page"] = a.substring(0,

            255), c["a.activitymap.link"] = 128 < d.length ? d.substring(0, 128) : d, c["a.activitymap.region"] = 127 < b.length ? b.substring(0, 127) : b, c["a.activitymap.pageIDType"] = f.pageName ? 1 : 0)

    };

Is this a correct understanding to the problem?

Is there a other solution to this problem other than modifying the ActivityMap module code?

Thanks.

Jantzen.Belliston​ Gigazelle​

[Gigazelle]

If it fixed it for you, then awesome. It looks like the removed part of code was a fallback to pageURL if pageName doesn't exist, so as long as you're defining pageName on every page, you should be good.