Mbox.js to At.js upgrade causing < Uncaught ReferenceError: CQ_Analytics is not defined > console error | Community
Skip to main content
ganeshboggavara
ganeshboggavara
Level 3
July 28, 2020
Solved

Mbox.js to At.js upgrade causing < Uncaught ReferenceError: CQ_Analytics is not defined > console error

  • July 28, 2020
  • 1 reply
  • 1331 views

Hi,

I recently got below Alert when logged into Adobe Target, so I started migrating mbox.js to at.js and as part of that installed Adobe TargetV2 Launch extension(we are using Adobe Launch for Tag Management) and modified the All Pages - Library loaded rule, and we had mbox.js calls replaced with , https://clientId.tt.omtrdc.net/rest/v1/delivery?    which i am thinking is pretty much the upgrade process, but we started seeing Uncaught ReferenceError: CQ_Analytics is not defined console error

 

Can someone let know what was missed? we are using AEM 6.5.5

We are also implementing Component Targeting using Target Engine, but the targeted experience is loading and the disappearing on the page for the components which had some action, Is that because of this as well? Can someone guide please?

Appreciate any responses!!

Thanks,

Ganesh

    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 ryanr7

    Hi @ganeshboggavara,

    So you have Target deployed via the new Launch extension now (good). In AEM do you have cloud service setup with Adobe Target? I'm guessing so if you are using the Target engine for targeting components. I'd check to see if you need to update that to look for at.js on the page instead of AEM loading it separately.

    -Ryan

    1 reply

    R
    Adobe Employee
    ryanr7Adobe EmployeeAccepted solution
    Adobe Employee
    July 29, 2020

    Hi @ganeshboggavara,

    So you have Target deployed via the new Launch extension now (good). In AEM do you have cloud service setup with Adobe Target? I'm guessing so if you are using the Target engine for targeting components. I'd check to see if you need to update that to look for at.js on the page instead of AEM loading it separately.

    -Ryan

      ganeshboggavara
      ganeshboggavaraAuthor
      Level 3
      July 30, 2020

      Hi @ryanr7,

      Thanks for the response, Yes we have AEM Target Cloud Service configured using IMS and we are pointing it to use at.js only, I don't see any option either in page properties or in component Target Engine selection dialog to specify to use at.js , Below is what I have set

       

       

       

      Thanks,

      Ganesh

       

       

        Terms & ConditionsAccessibility statement

        Loading footer...