Expand my Community achievements bar.

Why is adobe.target.event.CONTENT_RENDERING_FAILED event fired on pages outside page delivery scope?

Avatar

Level 2

I'm trying to identify via javascript if I'm on an experiment page: like a page within the page delivery scope. Therefore I tried to check on the following adobe target events:

 

At the moment I found that I can confirm I'm within a delivery page if the following event is fired:

adobe.target.event.REQUEST_SUCCEEDED

 

But then, this event is not fired on other pages within page delivery scope like the control variant or variant pages where clicktracking html is not available. I tried using the event:

adobe.target.event.CONTENT_RENDERING_FAILED


This last event fires on control and pages without the injected html, but also on any other page outside the page delivery scope.

Any suggestions on how to identify only pages within the page delivery scopes of the activity?

 

2 Replies

Avatar

Community Advisor

Hi @FerranSa  

If I  understood the question correctly, you want to determine whether a webpage is a part of delivery scope an Adobe Target activity, using at.js custom events, is that right?  And the page delivery scope refers to mean - where the activity is designed to run. 

Is this correct understanding? 

Avatar

Community Advisor

Hi @FerranSa ,

 

Content rendering failed due to wrapping mbox element missing, selector can not be found on the page.