CJA - Activity Map Link setup | Community
Skip to main content
L
Leyla-1
New Participant
September 8, 2025
Question

CJA - Activity Map Link setup

  • September 8, 2025
  • 1 reply
  • 553 views

Hello Adobe Community,

I have a question related to the Activity Map Link dimension setup in CJA. Please see the summary below. Any hints are appreciated.

Thank you!

 

********************

Desired state:

A single dimension that captures all user engagement clicks — both tabs/UI interactions (no link) and button or link clicks (navigational) — similar to how the Activity Map Link dimension works in AA without inflating the number of clicks. 

 

Current state:

We have a Custom Link (web.webInteraction.name) enabled in CJA, however, it's capturing both:

  • Collect call (Activity Map) → e.g., “Access the full report” 
  • Interact call → e.g., “Webtile CTA Click” 

As a result, the same action is recorded twice, doubling counts for link clicks in the Custom Link dimension. 

 

Question:

We explored exposing web.webInteraction.linkClicks.name, but that field isn’t available in our schema. What alternative approaches can we use to replicate the Activity Map Link dimension in CJA? Or do we need to adjust our Adobe Launch implementation for this?

 

Thank you!

1 reply

bjoern__koth
bjoern__koth
New Participant
September 8, 2025

Hi @leyla-1 

a few things upfront

  • ActivityMap is a legacy feature that does not exist in CJA anymore. It was built to create an overlay in the browser, so you could see aggregated page views and interactions while looking at your website
  • ActivityMap runs (always did, always will) "on the side" of your custom link tracking, so it is correct that you see a separate call for it.
    So, this feature is not polluting your data with useless information, it does what it should, and does it through a custom link tracking call.
  • ActivityMap clicks fill data in two locations in your collect/interact call.
    • events[0].data.__adobe.analytics.contextData.a.activitymap
    • events[0].xdm.web.webInteraction.name/URL/region

 

So much for the basics.

 

Now, if you want to suppress an ActivityMap call from firing, the best place to do so would be in the Web SDK's filterClickDetails callback that you find just under the section "Collect internal link clicks", named "Edit filter click details callback code" which is a custom code block you can edit as needed.

 

In there, you can do about anything like 

  • modifying/extending request data 
  • cancelling calls (return false)

If you want to figure out whether you are dealing with an ActivityMap click that is about to fire, you can inspect the content.clickedElement which is the HTML element that got clicked.

And with a little querying, you should be able to determine whether this click should trigger or not.

const triggersCustomLink = content?.clickedElement?.closest("[data-cmp-download-type]"); if (triggersCustomLink) return false;

As long as your stakeholders are ok with "losing" the implicit click tracking on the button/link, this should work.

Cheers from Switzerland!
    L
    Leyla-1Author
    New Participant
    September 9, 2025

    Hi @bjoern__koth ,

     

    Thank you for the quick reply and the helpful suggestions. They sparked some ideas. Since we’re still using Adobe Analytics, I don’t think suppressing Activity Map calls is the right approach for us at this point. Instead, I can take advantage of web.webInteraction.region along with some manual exclusion rules to build a custom link dimension. This configuration will allow us to exclude non-essential items, such as Target calls and “ContactUs Tracking: start,” etc. resulting in a cleaner and more reliable dataset for analyzing user page engagement.

     

    Thanks again for your help!

      bjoern__koth
      bjoern__koth
      New Participant
      September 9, 2025

      Hi @leyla-1,

      maybe also worth investigating, you can use the onBeforeEventSend callback in a similar way, enriching your Activity Map click tracking with other props/eVars you would want to track together with the default Activity Map fields.

       

      This would still fire the other call, just in case if you want to add more context to your Activity Map in general.

      // onBeforeEventSend // Modify content.xdm or content.data as necessary. There is no need to wrap the // code in a function or return a value. For example: // content.xdm.web.webPageDetails.name = "Checkout"; content.data = content.data || {}; content.data.__adobe = content.data.__adobe || {}; content.data.__adobe.analytics = content.data.__adobe.analytics || {}; let s = content.data.__adobe.analytics; let activityMap = s?.contextData?.a?.activitymap; if (activityMap) { s.eVar1 = _satellite.getVar("some data element", event); s.events = "event99"; // NOTE: no need for linkTrackEvents and linkTrackVars anymore }

       

      Cheers from Switzerland!
        Terms & ConditionsAccessibility statement

        Loading footer...