What are possible reasons why ClearVariable fails? | Community
Skip to main content
Level 6
February 21, 2019
Solved

What are possible reasons why ClearVariable fails?

  • February 21, 2019
  • 34 replies
  • 31627 views

We are currently mainly using direct call rules for our tracking. Even the page view itself is a direct call rule, as we had the pageBottom fire when it shouldn't (SPA not finished initializing). All our rules follow the same pattern in the action section: 1-n Set Variables, Send Beacon, Clear Variables.

One of these Set Variables actions is responsible to set s.products and s.events only on product detail pages, to track its view (prodView and a custom event). I now have the strange behaviour that these are not cleared at the end: The product detail page has multiple tabs which we only track minimalistic with the title of the tab, a custom event for tab click and some standard variables which are tracked in a doPlugin method. But the first tab I click also contains s.products and s.events values from the page view rule fired before. The second and any other on page rule are fine and do not contain them, as if the Clear Variables from the tab click rule worked and the one from the page view didn't. Is there any way to debug the Clear Variable action to see if it really isn't executed?

I debugged the tab click rule and there s.products is still populated the first time the rule gets fired.

EDIT: Could there be some issues, if this tab click rule wasn't modified for a while, but we now use a newer version of the Analytics Extension? Do you have to "touch" every single rule if you update one of the extensions that are used within the rule?

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 josnyder1

I've seen problems with the ManageVars plugin where it overwrites the s.t function.  It looks like you are having this problem.  Check your doPlugin custom code to see if this is the case.

34 replies

Level 4
February 21, 2019

How are your different rules and their corresponding action blocks set up?

I think the issue your seeing is stemming from something you hinted at in this quote, but I'm not sure without more info:

Where are you doing the logic to set s.products and s.events?  Are you using other extensions, , setvars custom code section, or custom code blocks?

Level 6
February 25, 2019

I only use the basic extensions for Analytics: Core, Context Hub, Experience Cloud ID Service, Analytics Extension.

Most Set Variables actions use custom code, but I don't see what could be an issue with that. This used to work until recently, so my guess is Analytics Extension 1.6 or AppMeasurement 2.11 respectively introduced a bug with s.t() so the variables aren't properly cleared. They still get cleared with s.tl() calls.

I also opened a ticket with support for this as we are nearing our next release on the weekend and this is now a major problem on our side.

Level 6
February 25, 2019

I did some further testing and as we are hosting the scripts ourselfs, I was able to use the old AppMeasurement.js on our test environment. There I don't have the problem. So I can at least confirm that AppMeasurement 2.11.0 introduced a bug which wasn't there in 2.10.0

So for all others I recommend not to upgrade your Analytics Extension to 1.16.0 which includes AppMeasurement 2.11.0

miikkal3149476
Level 2
February 25, 2019

We have ran into this same problem after updating to newest Analytics Extension, Clear Variables is not working as it should, and old events are sent in next analytics call, where they should already be cleared.

Please fix this asap, also have opened support ticket about this.

Level 6
February 25, 2019

Good to know that I am not the only one and someone else confirmes the issue. Updated my ticket, so they are aware that there is another ticket around with the same issue.

Level 6
March 6, 2019

I just found another strange behavior with AppMeasurement 2.11:

On the Shopping Cart Page two direct call rules are fired:

page-load: actual page-view with s.t()

cart-add: Cart addition with s.tl()

The problem is, both Rules overlap and do strange things with the tracking object:

s.products is only populated in cart-add, but I already see the product string in the page-load call. In cart-add s.products is then empty again.

here my Log from DTM Debugger (Who doesn't seem to know s.products):

VM805:1   Rule "DC: "page-load" - s.t()" fired.

VM805:1   [Adobe Analytics] Set variables on the tracker.

VM805:1   [Adobe Analytics] Applying the following properties on tracker: "{"eVar44":"","eVar67":"Inhaltsbereich","eVar75":"","eVar76":"","prop67":"D=v67","linkTrackVars":"eVar44,eVar67,eVar75,eVar76,prop67,campaign"}".

VM805:1   [Adobe Analytics] Set variables on the tracker.

VM805:1   [Adobe Analytics] Applying the following properties on tracker: "{"linkTrackVars":"eVar44,eVar67,eVar75,eVar76,prop67,campaign"}".

VM805:1   [Adobe Analytics] Set variables on the tracker.

VM805:1   [Adobe Analytics] Applying the following properties on tracker: "{"linkTrackVars":"eVar44,eVar67,eVar75,eVar76,prop67,campaign"}".

VM805:1   [Adobe Analytics] Set variables on the tracker.

VM805:1   [Adobe Analytics] Applying the following properties on tracker: "{"linkTrackVars":"eVar44,eVar67,eVar75,eVar76,prop67,campaign,eVar91"}".

VM805:1   [Adobe Analytics] Set variables on the tracker.

VM805:1   [Adobe Analytics] Applying the following properties on tracker: "{"linkTrackVars":"eVar44,eVar67,eVar75,eVar76,prop67,campaign,eVar91"}".

VM805:1   [Adobe Analytics] Set variables on the tracker.

VM805:1   [Adobe Analytics] Applying the following properties on tracker: "{"linkTrackVars":"eVar44,eVar67,eVar75,eVar76,prop67,campaign,eVar91"}".

VM805:1   [Adobe Analytics] Set variables on the tracker.

VM805:1   [Adobe Analytics] Applying the following properties on tracker: "{"linkTrackVars":"eVar44,eVar67,eVar75,eVar76,prop67,campaign,eVar91"}".

VM805:1   [Adobe Analytics] Set variables on the tracker.

VM805:1   [Adobe Analytics] Applying the following properties on tracker: "{"linkTrackVars":"eVar44,eVar67,eVar75,eVar76,prop67,campaign,eVar91"}".

VM805:1   [Adobe Analytics] Firing page view beacon.

VM805:1   [Adobe Analytics] Clear variables.

VM805:1   Rule "DC: "cart-interaction"" fired.

VM805:1   [Adobe Analytics] Set variables on the tracker.

VM805:1   [Adobe Analytics] Applying the following properties on tracker: "{"linkTrackVars":"eVar44,eVar67,eVar75,eVar76,prop67,campaign,eVar91"}".

VM805:1   [Adobe Analytics] Firing link track beacon using the values: {"linkType":"o","linkName":"Cart Interaction"}.

VM805:1   [Adobe Analytics] Clear variables.

Level 2
March 8, 2019

Got the same problem too. Searched for hours, I'm glad to hear I'm not the only one (though it problematic :-) )

Level 6
March 11, 2019

@all

Please provide support with reproducible cases. Our test environments aren't accessible from outside, so they struggle with my ticket. But if you guys have accessible test environments where support can try to reproduce the issue, it would help them fix it.

Level 2
March 14, 2019

Opened an incident with client care : [Incident: 190311-000076] if that can help.

We have not found a solution yet.

miikkal3149476
Level 2
March 14, 2019

Hi, Yeah I also gave demo session to customer support, but haven't got any solution or information yet. They just said they try to reproduce it in their environment. Us like many others don't have open test environment for outsiders to access.