Experience Cloud Triggersnot working with AEP Web SDK extension not working | Community
Skip to main content
Level 3
July 25, 2023
Solved

Experience Cloud Triggersnot working with AEP Web SDK extension not working

  • July 25, 2023
  • 1 reply
  • 662 views

Hi team

 

We are using AEP web SDK extension for sending data to adobe analytics through launch data collection.

Triggeres are not working for this kind of setup. 

 

is there something i am missing ? any specific configuration needed to enable triggers for web sdk extension?

 

Thanks

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

Perhaps you can help clarify what you are experiencing...

 

A Trigger is a trigger... it doesn't matter if you are running custom code, traditional analytics, web SDK analytics, some other extension.....

 

Have you tried enabling debug mode in your browser's console?

 

// Turn on debugging: _satellite.setDebug(true); // Turn off debugging: _satellite.setDebug(false);

 

This should add information into your browsers console about what Launch is doing, what rules are being triggered, in what order, etc...

 

This will help you determine if your rule is triggered, but maybe you have a problem with your WebSDK implementation.. or maybe your trigger isn't working, and it has nothing to do with the WebSDK at all....

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
July 25, 2023

Perhaps you can help clarify what you are experiencing...

 

A Trigger is a trigger... it doesn't matter if you are running custom code, traditional analytics, web SDK analytics, some other extension.....

 

Have you tried enabling debug mode in your browser's console?

 

// Turn on debugging: _satellite.setDebug(true); // Turn off debugging: _satellite.setDebug(false);

 

This should add information into your browsers console about what Launch is doing, what rules are being triggered, in what order, etc...

 

This will help you determine if your rule is triggered, but maybe you have a problem with your WebSDK implementation.. or maybe your trigger isn't working, and it has nothing to do with the WebSDK at all....