Hi everyone,
just finishing up the AEP Web SDK migration and ran into an issue with activity map and exit link tracking, enabled the click tracking in the extension configuration, still doesn't work (snapshot attached).
Anyone else facing the same issue?
Thanks!
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @AnuragSh12
same as @Jennifer_Kunz I have the same setup running without problems for me.
Though somethimes you may want to customize it a little.
What you can do is provide additional code in the "Provide filter click properties callback code" at the bottom of your screenshot.
This may help you understand a little bit better what's happening since this code runs before the click tracking event is sent.
For instance, when you have multiple domains that you want to treat as internal, you can use this code to make sure they are not treated as exit.
/*
* Use this custom code block to adjust or filter click data. You can use the following variables:
* content.clickedElement: The DOM element that was clicked
* content.pageName: The page name when the click happened
* content.linkName: The name of the clicked link
* content.linkRegion: The region of the clicked link
* content.linkType: The type of link (typically exit, download, or other)
* content.linkUrl: The destination URL of the clicked link
* Return false to omit link data.
*/
// rewrite exit links to be of type "other" if domains are internal
const internalDomains = ["mydomain.com"];
if (content.linkType === "exit" && internalDomains.some(domain => content.linkUrl.includes(domain))) {
content.linkType = "other";
}
Likewise, you can add console logs in here to check whether the click is actually captured
// make sure you have enabled console logging
_satellite.setDebug(true);
_satellite.logger.debug(">>> Click captured");
By "doesn't work", do you mean you aren't seeing click events sent to AEP when looking in the network tab or AEP debugger? Is that true of all of the click events? Are your page view events working?
I have the same set up as your screenshot, and do see click tracking working - you can see it at https://www.digitaldatatactics.com/?testEdge=true if you want.
Hi @AnuragSh12
same as @Jennifer_Kunz I have the same setup running without problems for me.
Though somethimes you may want to customize it a little.
What you can do is provide additional code in the "Provide filter click properties callback code" at the bottom of your screenshot.
This may help you understand a little bit better what's happening since this code runs before the click tracking event is sent.
For instance, when you have multiple domains that you want to treat as internal, you can use this code to make sure they are not treated as exit.
/*
* Use this custom code block to adjust or filter click data. You can use the following variables:
* content.clickedElement: The DOM element that was clicked
* content.pageName: The page name when the click happened
* content.linkName: The name of the clicked link
* content.linkRegion: The region of the clicked link
* content.linkType: The type of link (typically exit, download, or other)
* content.linkUrl: The destination URL of the clicked link
* Return false to omit link data.
*/
// rewrite exit links to be of type "other" if domains are internal
const internalDomains = ["mydomain.com"];
if (content.linkType === "exit" && internalDomains.some(domain => content.linkUrl.includes(domain))) {
content.linkType = "other";
}
Likewise, you can add console logs in here to check whether the click is actually captured
// make sure you have enabled console logging
_satellite.setDebug(true);
_satellite.logger.debug(">>> Click captured");
Views
Likes
Replies