I am trying to debug a page but the analytics won't show up. It worked for me earlier but can someone help me understand what is wrong with it. | Community
Skip to main content
S
ShwetaSh
January 20, 2025
Solved

I am trying to debug a page but the analytics won't show up. It worked for me earlier but can someone help me understand what is wrong with it.

  • January 20, 2025
  • 2 replies
  • 837 views

I am trying to debug a page. The page is connected to analytics but still debugger is not tracking any hits. What can be the possible reason for this? It used to work for me earlier, but lately, I am unable to track hits on the page. Please share a resolution.

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 bjoern__koth

Hi @shwetash ,

 

[UPDATE]I took the freedom to google the page behind your screenshot, hope you don't mind.

You have a consent issue. As soon as I release all consent with approveAll, I see your page view event firing.

So, also seeing that you are using a OneTrust CookiePro setup, this is likely a consent management setup issue.

OneTrust loaded

 

I see the following OptanonConsent Cookie

isGpcEnabled=0&datestamp=Mon Jan 20 2025 18:54:27 GMT+0100 (Central European Standard Time)&version=202210.1.0&isIABGlobal=false&hosts=&consentId=e63c418c-5bd9-4887-98e4-c1634300d4fd&interactionCount=0&landingPath=NotLandingPage&groups=1:1,2:0,3:0,4:0&geolocation=CH&AwaitingReconsent=false

 

so presumably, you are not properly initialising the previous consent in the Visitor ID service.

 

 

This should return an object with opt-in settings based on this cookie that onetrust sets.

Below is a sample Data Element that properly initializes the Adobe tools based on other Data Elements for Analytics, Target and Visitor ID service.

// initializes the Adobe opt-in service (extension > Visitor ID Service) var optInSettings = { aa: _satellite.getVar('JS - Consent - Analytics'), ecid: _satellite.getVar('JS - Consent - Analytics'), target: _satellite.getVar('JS - Consent - Targeting'), // unused aam: false, adcloud: false, campaign: false, livefyre: false, mediaaa: false, } return optInSettings;

 

---------------

[Initial message]


first of all, are you sure a request should be triggered?

 

Possible causes that come to my mind
1. the debugger is not properly attached to the underlying page -> Try reloading the page below. Can you see any "/ss" requests in the network tab. Alternatively, you can also use other browser extensions like Omnibug or the Universal Adobe Debugger which is useful for many other tags as well

2. cookie consent issue. Are you using a cookie consent platform and have opt in enabled on the visitor ID extension? -> try executing "adobe.optIn.approveAll()" in the console and see if this releases your requests from being queued

See also https://experienceleague.adobe.com/en/docs/id-service/using/implementation/opt-in-service/launch

2 replies

bjoern__koth
Community Advisor and Adobe Champion
bjoern__kothCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
January 20, 2025

Hi @shwetash ,

 

[UPDATE]I took the freedom to google the page behind your screenshot, hope you don't mind.

You have a consent issue. As soon as I release all consent with approveAll, I see your page view event firing.

So, also seeing that you are using a OneTrust CookiePro setup, this is likely a consent management setup issue.

OneTrust loaded

 

I see the following OptanonConsent Cookie

isGpcEnabled=0&datestamp=Mon Jan 20 2025 18:54:27 GMT+0100 (Central European Standard Time)&version=202210.1.0&isIABGlobal=false&hosts=&consentId=e63c418c-5bd9-4887-98e4-c1634300d4fd&interactionCount=0&landingPath=NotLandingPage&groups=1:1,2:0,3:0,4:0&geolocation=CH&AwaitingReconsent=false

 

so presumably, you are not properly initialising the previous consent in the Visitor ID service.

 

 

This should return an object with opt-in settings based on this cookie that onetrust sets.

Below is a sample Data Element that properly initializes the Adobe tools based on other Data Elements for Analytics, Target and Visitor ID service.

// initializes the Adobe opt-in service (extension > Visitor ID Service) var optInSettings = { aa: _satellite.getVar('JS - Consent - Analytics'), ecid: _satellite.getVar('JS - Consent - Analytics'), target: _satellite.getVar('JS - Consent - Targeting'), // unused aam: false, adcloud: false, campaign: false, livefyre: false, mediaaa: false, } return optInSettings;

 

---------------

[Initial message]


first of all, are you sure a request should be triggered?

 

Possible causes that come to my mind
1. the debugger is not properly attached to the underlying page -> Try reloading the page below. Can you see any "/ss" requests in the network tab. Alternatively, you can also use other browser extensions like Omnibug or the Universal Adobe Debugger which is useful for many other tags as well

2. cookie consent issue. Are you using a cookie consent platform and have opt in enabled on the visitor ID extension? -> try executing "adobe.optIn.approveAll()" in the console and see if this releases your requests from being queued

See also https://experienceleague.adobe.com/en/docs/id-service/using/implementation/opt-in-service/launch

Cheers from Switzerland!
    Harveer_SinghGi1
    Community Advisor and Adobe Champion
    Harveer_SinghGi1Community Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    January 20, 2025

    Hi @shwetash,

    Looking at the screen shot it looks like AA library has loaded on your website. I'd perform few initial checks as below to investigate,

    • Run _satellite.property and _satellite.environment commnads in browser console to check if you are laoding the right property and environment on this site
    • Enable tag debugging by running _satellite.setDebug("true"); command in in browser console or through AEP debugger under Experience Platform Tags -> Configuration -> Console Logging Checkbox. After this reload the page and,
      • See if the rule that is supposed to send the tracking call that you are expecting is even triggering or not.
      • If that rule  is it throwing any error then investigate further accordingly.
      • If that rule is triggering successfully but you still don't see the call then check the rule action related to the AA send beacon and make sure it is published

    Cheers!

      Terms & ConditionsAccessibility statement

      Loading footer...