Expand my Community achievements bar.

Join us for the next Community Q&A Coffee Break on Tuesday April 23, 2024 with Eric Matisoff, Principal Evangelist, Analytics & Data Science, who will join us to discuss all the big news and announcements from Summit 2024!
SOLVED

Experience Cloud Triggersnot working with AEP Web SDK extension not working

Avatar

Level 3

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

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

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....

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

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....