Expand my Community achievements bar.

SOLVED

ActivityMap

Avatar

Level 3

Hey guys, I am working with Adobe analytics and adobe launch integrating with AEM, and I am getting some trouble with integrating Activity Map metrics on aem pages, I already tried to follow the articles and got nothing at all, I think that this could be something to do with UsersGroup on Analytics.

If someone please could provide me a updated article It probably would help a lot.

1 Accepted Solution

Avatar

Correct answer by
Employee

Can you elaborate on what issue you are seeing with Activity Map?  For example, are you having trouble getting the Activity Map data to be sent on the image requests or is it more of a problem with rendering the overlays?

Some things you may consider checking:

  1. On you web page, open up Dev Tools and, in the console, run the command 's_c_il'.  This should return an array of analytics related objects, including the activity map module.  This is a good way to confirm that the library is loading as expected.
  2. If the library is loading correctly, then click a link on the page and review the subsequent analytics image request.  You should see context data (.ActivityMap) included in the calls, suggesting that Analytics is collecting the Activity Map data
  3. If data is collecting, then it is an overlay rendering issue.  Login to the Activity Map plugin and check the settings to confirm you are pointing at the same report suite and page name as observed in step 2.  For overlays to render correctly, the report suite, pagename, link region, and link name all need to match.

Note: There are other reasons that could contribute to overlays not showing up correctly.  You may consider reaching out to Customer Care if the steps above don't yield any results.

Also, I didn't see a documentation link in your post.  Happy to look for an updated document if you can provide the link

I hope that helps.

View solution in original post

3 Replies

Avatar

Correct answer by
Employee

Can you elaborate on what issue you are seeing with Activity Map?  For example, are you having trouble getting the Activity Map data to be sent on the image requests or is it more of a problem with rendering the overlays?

Some things you may consider checking:

  1. On you web page, open up Dev Tools and, in the console, run the command 's_c_il'.  This should return an array of analytics related objects, including the activity map module.  This is a good way to confirm that the library is loading as expected.
  2. If the library is loading correctly, then click a link on the page and review the subsequent analytics image request.  You should see context data (.ActivityMap) included in the calls, suggesting that Analytics is collecting the Activity Map data
  3. If data is collecting, then it is an overlay rendering issue.  Login to the Activity Map plugin and check the settings to confirm you are pointing at the same report suite and page name as observed in step 2.  For overlays to render correctly, the report suite, pagename, link region, and link name all need to match.

Note: There are other reasons that could contribute to overlays not showing up correctly.  You may consider reaching out to Customer Care if the steps above don't yield any results.

Also, I didn't see a documentation link in your post.  Happy to look for an updated document if you can provide the link

I hope that helps.

Avatar

Level 3

Actually we are trying to get metrics like page views directly on each page info on AEM, not on the page rendered but on the page as a node on the interface of AEM, as we know that is one its capability, but I am thinking it has something to do with the fact we are using Adobe Launch as a middle. I don't know if you understood so, down bellow you can see what I am saying:page pre info.jpg

If you have something in mind please let me know.

Avatar

Employee

Oh, I see.  You are trying to load page-level metrics from Analytics into the AEM page.  That integration can be a bit tricky.  The biggest issue I have seen with the integration is a mismatch in the pagename value that AEM uses in its API queries and the pagename values used for Analytics tracking.

I would recommend opening a support ticket with the AEM Customer Care team to confirm if this is a mismatch of the pagename and to discuss configuration options to correct the integration.  They will need some account specific information, such as your report suite ID, to track down the root cause.