Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Cannot send beacon: TypeError: window.location.query is not a function

Avatar

Avatar
Validate 1
Level 1
puckingfeachy
Level 1

Likes

0 likes

Total Posts

4 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
puckingfeachy
Level 1

Likes

0 likes

Total Posts

4 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile
puckingfeachy
Level 1

12-05-2021

Hi there -

Hoping you can help me understand why I a getting the error: 

Cannot send beacon: TypeError: window.location.query is not a function

 

Here is the window.location.query code I found in the Launch library that I think is causing the issue:

settings: {
orgId: "Xreplaced the value hereX@AdobeOrg",
customSetup: {
source: function() {
console.log(window.location.query("cmp"))
}
}, 

 

In Launch, I have a data element %campaignid% that is set to capture value from cmp query string parameter. 

puckingfeachy_0-1620842678731.png

 

This value is passed on global page view and one other rule.

 

The page view isn't showing up in Adobe.

 

Am I missing something? Is there something else I can share to make the scenario more clear?

 

Thanks,

 

PFeach

 

Accepted Solutions (0)

Answers (2)

Answers (2)

Avatar

Avatar
Boost 3
Level 1
tim_funk
Level 1

Likes

3 likes

Total Posts

18 posts

Correct Reply

0 solutions
Top badges earned
Boost 3
Contributor
Applaud 5
Shape 1
Boost 1
View profile

Avatar
Boost 3
Level 1
tim_funk
Level 1

Likes

3 likes

Total Posts

18 posts

Correct Reply

0 solutions
Top badges earned
Boost 3
Contributor
Applaud 5
Shape 1
Boost 1
View profile
tim_funk
Level 1

13-05-2021

I see the Storage duration is set to session - So I suspect the initial page view was missing that parameter so that value carried as empty the rest of the session.

 

https://experienceleague.adobe.com/docs/launch/using/ui/data-elements.html?lang=en

Avatar

Avatar
Publish 1
MVP
yuhuisg
MVP

Likes

180 likes

Total Posts

541 posts

Correct Reply

106 solutions
Top badges earned
Publish 1
Affirm 100
Springboard
Bedrock
Validate 1
View profile

Avatar
Publish 1
MVP
yuhuisg
MVP

Likes

180 likes

Total Posts

541 posts

Correct Reply

106 solutions
Top badges earned
Publish 1
Affirm 100
Springboard
Bedrock
Validate 1
View profile
yuhuisg
MVP

13-05-2021

I'm not sure where that code is coming from. I'm pretty sure it's not from the Core extension itself. It looks like it could be coming from a Condition or Action in one of your Rules.

Anyway, try replacing "window.location.query" with just "location.query".