Asset Insights Tracker in Adobe Launch | Community
Skip to main content
N
NingLaoShi
Level 2
April 20, 2023
Solved

Asset Insights Tracker in Adobe Launch

  • April 20, 2023
  • 2 replies
  • 1059 views

Hi, I am enabling the asset insights tracker for an AEM page. I have created 3 rules for this:

1. Asset Impression

2. Asset Click

3. Asset Click without destination

 

Here is my configuration:

 

I have several problems here:

1. The page load and click beacon are firing twice

 

2. I want my asset.idlist on my link click beacon, but it is only showing on page load beacon, how can I add this?

 

Can you guys help me troubleshooting this? Thank you so much.

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Jennifer_Dungan

While I don't use that function... perhaps the solution is to use those AEM triggers to set variables, but not yet send the beacon?

 

Basically, use those triggers to set dimensions and metrics (so that they are "ready"), then have one tracking call that sends your core tracking plus the values that were set by these functions?

 

You will have to make sure that all those calls happen in the right order (so that the AEM triggers are fired first before the rule with the send beacon).

 

Try turning on debug mode for your Launch implementation...

 

In your console, run the following:

_satellite.setDebug(true)

 

This will allow you to see all the steps (and order) that things are being run in your Launch implementation.

 

You can turn it off by using:

_satellite.setDebug(false)

2 replies

N
NingLaoShiAuthor
Level 2
April 20, 2023

My problem now is asset.idlist is not showing in my link click beacon. It only shows in page load beacon

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
April 20, 2023

While I don't use that function... perhaps the solution is to use those AEM triggers to set variables, but not yet send the beacon?

 

Basically, use those triggers to set dimensions and metrics (so that they are "ready"), then have one tracking call that sends your core tracking plus the values that were set by these functions?

 

You will have to make sure that all those calls happen in the right order (so that the AEM triggers are fired first before the rule with the send beacon).

 

Try turning on debug mode for your Launch implementation...

 

In your console, run the following:

_satellite.setDebug(true)

 

This will allow you to see all the steps (and order) that things are being run in your Launch implementation.

 

You can turn it off by using:

_satellite.setDebug(false)
Terms & ConditionsAccessibility statement

Loading footer...