Global variables not sent with "Send Beacon" | Community
Skip to main content
Level 6
June 5, 2018
Solved

Global variables not sent with "Send Beacon"

  • June 5, 2018
  • 3 replies
  • 3991 views

I have configured a bunch of Global Variables in the Analytics Extension, but my page load rule doesn't send them. It only executes the ones set in the custom code section of the Analytics Extension. I don't have any overlays in the "Set Variables" action at the moment it is actually empty. The only thing I see in the tracking call are the props that are set as duplicate frrom the eVars. But even this doesn't work in any other rule on the page, there nothing except the explicitly set eVars and props are sent and nothing from the Global Variables.

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 thomas_amsler

I completely refactred my Launch rules, so no, this is no longer relevant. I do everything within a doPlugins method as I anyway have som custom code I need and thus prefer to have all variable setter in one place instead of spread between the GUI and the custom code.

3 replies

Gigazelle
Adobe Employee
Adobe Employee
November 16, 2018

Is this still an issue for you? I have several variables defined in my global settings, and they appear to be tracking just fine.

If it is still an issue for you, you can try using a rule that triggers unconditionally after every hit.

thomas_amslerAuthorAccepted solution
Level 6
November 19, 2018

I completely refactred my Launch rules, so no, this is no longer relevant. I do everything within a doPlugins method as I anyway have som custom code I need and thus prefer to have all variable setter in one place instead of spread between the GUI and the custom code.

Gigazelle
Adobe Employee
Adobe Employee
November 19, 2018

Good to know, thanks for the response!

Have you already read through the Analytics extension Plugin support thread? Adobe plans to add something akin to doPlugins in the Launch UI, so if you're able to share your use case in that thread, we can ensure the feature is applicable to you once it's released.