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

Avatar

Avatar
Validate 1
Level 2
ganeshboggavara
Level 2

Likes

2 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 1
Give Back 5
View profile

Avatar
Validate 1
Level 2
ganeshboggavara
Level 2

Likes

2 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 1
Give Back 5
View profile
ganeshboggavara
Level 2

27-07-2020

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

image-20200715-141805 (1).pngCapture.PNG

 

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

Accepted Solutions (0)

Answers (1)

Answers (1)

Avatar

Avatar
Give Back 25
Employee
ryanr701
Employee

Likes

202 likes

Total Posts

224 posts

Correct reply

90 solutions
Top badges earned
Give Back 25
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile

Avatar
Give Back 25
Employee
ryanr701
Employee

Likes

202 likes

Total Posts

224 posts

Correct reply

90 solutions
Top badges earned
Give Back 25
Give Back 10
Give Back 5
Give Back 3
Give Back
View profile
ryanr701
Employee

29-07-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