What are possible reasons why ClearVariable fails?

Avatar

Avatar

thomas_amsler

Avatar

thomas_amsler

thomas_amsler

21-02-2019

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?

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

josnyder

Employee

Avatar

josnyder

Employee

josnyder
Employee

22-10-2019

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.

Answers (33)

Answers (33)

Avatar

Avatar

miikkal3149476

Avatar

miikkal3149476

miikkal3149476

25-02-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.

Avatar

Avatar

thomas_amsler

Avatar

thomas_amsler

thomas_amsler

25-02-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

Avatar

Avatar

FaresAldik

Avatar

FaresAldik

FaresAldik

22-10-2019

Hi josnyder​ ! You've found my issue. It's was the manageVars plugin. It was present in the older code and the clearVars function was being overwritten by the plugin. I've completely removed the plugins (manageVars and clearVars). And now we're good to go!

1846971_pastedImage_1.png

Thank you for sharing this tip. I was pulling my hair on this. 

Avatar

Avatar

miikkal3149476

Avatar

miikkal3149476

miikkal3149476

11-06-2019

Hi,

I have upgraded to the new version of extensions and looks like the clear variables issue is fixed. I'll report back if I find any other issues, but for now, it seems to work.

Avatar

Avatar

thebenrobb

Employee

Avatar

thebenrobb

Employee

thebenrobb
Employee

17-04-2019

Quick summary of the issue: AppMeasurement 2.13 was released last week which addressed the clearVars() issue - I actually don't know how far back that issue has existed, but it was for sure in 2.12 and presumably 2.11 and previous versions as well.  It was made available within DTM as AppMeasurement 2.13 and was contained within the Analytics Launch extension version 1.7.3.

Unfortunately, AppMeasurement 2.13 contained a different bug affecting ECID.  When that bug was discovered, we decided the quickest fix was to roll AppMeasurement back to 2.12.  This had the impact taking care of the ECID issue, but reintroducing the clearVars issue.

This rolled back version (2.12) that has no ECID issue, but does have a clearVars() issue is available with the Launch Analytics extension version 1.7.4 (and within DTM as AppMeasurement 2.13.1).

The Analytics team is working on an updated version of AppMeasurement that fixes the clearVars() issue and does not break ECID.  We expect that to be available in the coming weeks.

Avatar

Avatar

thomas_amsler

Avatar

thomas_amsler

thomas_amsler

11-06-2019

We can't test this just yet, as there is a minor release upcomming and we do not have the testing resources to risk a stil not working version. We'll test it during the summer.

Avatar

Avatar

AiThanh

Avatar

AiThanh

AiThanh

07-06-2019

It seems that the clearVars was fixed within the latest release: https://docs.adobelaunch.com/extension-reference/web/adobe-analytics-extension/adobe-analytics-relea...

Have anyone been successful with it? We still have troubles clearing the variables though.

Avatar

Avatar

thomas_amsler

Avatar

thomas_amsler

thomas_amsler

28-03-2019

I've got an update from support:

Quick update from Engineering. They mentioned that they have a fix in place and they should be able to push it to users within the next couple of weeks once they have tested it. I will updated you once the fix is pushed. Thank you for your patience in the meantime.

Avatar

Avatar

josnyder

Employee

Avatar

josnyder

Employee

josnyder
Employee

10-10-2019

I have not been able to reproduce the clearVars issue you reported.  Could you give me some more information such as a link to a page where you see the problem or a link to the Launch package?

Avatar

Avatar

thebenrobb

Employee

Avatar

thebenrobb

Employee

thebenrobb
Employee

10-10-2019

I've asked the Analytics team to take a look.

Avatar

Avatar

jillianc9978960

Avatar

jillianc9978960

jillianc9978960

10-10-2019

I am also seeing this issue again after adding 2 new variables to the custom page code of the AA Extension.

Avatar

Avatar

FaresAldik

Avatar

FaresAldik

FaresAldik

10-10-2019

Hi,

I’ve been using the AA Extension 1.7.8 (Adobe Analytics - Adobe Systems  v1.7.8 using AM 2.17.0), and I seem to have a resurgence of a failing Action Type: Clear Variables (which calls the s.clearVars). I’ve debugged it and the original s.clearVars(); works if taken directly from that 2.17.0 AM.js. But for some reason when it’s rendered through Launch, on execution, the function s.clearVars is replaced with an empty call like so:  … see screenshot … that last one doesn’t clear any variables.

image (6).png

I do see the calls made in the console logging:

image (7).png

Under the Launch Developers Slack, there has been a ticket opened in Adobe's product team. But I'm not certain if I'm the only one seeing this issue. In fact, I'm second guessing my error because when I look at the AA extension release notes, I don't even see the 1.7.8 extension release notes:

2019-10-10_12-39-42.png

I wish I didn't update my AA Extension when it proposed me ;-/

Avatar

Avatar

ggiles_analytic

Avatar

ggiles_analytic

ggiles_analytic

10-06-2019

After the update, clearVars is working more in line with what I expected. I did run into some issues with subsequent media analytics calls (from Heartbeat) having their associated contextData cleared, but I found a workaround by calling s.registerPostTrackCallback and clearing linkTrackVars/linkTrackEvents

Avatar

Avatar

thomas_amsler

Avatar

thomas_amsler

thomas_amsler

14-05-2019

Here the update I got from support last week, which is a bit less positive than your information thebenrobb​:

"Quick update. Engineering mentioned that they don't have a solid fix date yet since they are currently working through some issues while testing the fix. They would let us know once they have a more solid fix date and resolution."

Avatar

Avatar

thebenrobb

Employee

Avatar

thebenrobb

Employee

thebenrobb
Employee

13-05-2019

Unofficially, I've heard that the new version of AppMeasurement is being tested now.  I'd anticipate AppMeasurement itself will be released a little before a Launch extension with that same update.  I'd probably set my expectations for another week or two.

Avatar

Avatar

ggiles_analytic

Avatar

ggiles_analytic

ggiles_analytic

13-05-2019

Has there been any development on the fix/timelines for this issue?

Thanks,

Avatar

Avatar

thebenrobb

Employee

Avatar

thebenrobb

Employee

thebenrobb
Employee

29-04-2019

It appears that AppMeasurement 2.11 shipped in Analytics extension 1.6.0 on ~February 11.

Avatar

Avatar

Jennifer_Kunz

MVP

Avatar

Jennifer_Kunz

MVP

Jennifer_Kunz
MVP

29-04-2019

Do we know at what point this issue started? In what version of the Analytics Extension?

Avatar

Avatar

thomas_amsler

Avatar

thomas_amsler

thomas_amsler

17-04-2019

Thank you very much for the clear explanation. Though it will be too late for our next release, because it leaves us not enough time to retest everything. Looking forward to 2.14, which is then hopefully the next stable version without either of the two major bugs.

What I can say, 2.10 works for us as expected, only since 2.11 did we have problems and are thus staying with 2.10 until we can then test the next version thoroughly.

Avatar

Avatar

thomas_amsler

Avatar

thomas_amsler

thomas_amsler

16-04-2019

I just got an update from support, they claim that the latest version of the Analytics Extension (v1.7.4) should contain the fix for this issue. The included AppMeasurement is now on version 1.12.

EDIT:

My first impression was good, but now it seems the problem persists on my side. And one thing else seems to have broken. Each click on the webpage fires a tracking call, even though there isn't any rule involved. I get back to support.

Avatar

Avatar

settytb1

Employee

Avatar

settytb1

Employee

settytb1
Employee

18-03-2019

Hi all,

We are investigating the issue in relation to the latest version of the Analytics Launch extension. 

Thanks,

Seth

Avatar

Avatar

Jennifer_Kunz

MVP

Avatar

Jennifer_Kunz

MVP

Jennifer_Kunz
MVP

18-03-2019

It sounds like this is actually a defect (with the analytics extension), based on discussions with the product folks- something to do with the timing on pageBottom if you are using the Experience Cloud ID service. I believe it's been communicated to the folks in charge of that extension so hopefully there will be a fix before long.

Avatar

Avatar

sfabri

Avatar

sfabri

sfabri

14-03-2019

miikkal3149476 That is exactly the solution the customer care suggested to me this morning
Answered the same as you, something in the realm of : "It fixes the event issues but unfortunately half my variables are gone and the s.product as well. We cannot use this ".

Avatar

Avatar

miikkal3149476

Avatar

miikkal3149476

miikkal3149476

14-03-2019

Yeah, that is true, but then we'd need to know when they do this. As we do some changes and tweaks in dev all the time, so we can't have this issue there all the time.

Our current "fix" for this is, that we have clear variables both start and the end of the tracking. But that's not a long term solution as then we cannot use global variables on these rules.

Avatar

Avatar

sfabri

Avatar

sfabri

sfabri

14-03-2019

Hi guys,
If Support/customer care do not have access to your tests environement it can still test it in Production with a tool to replace the Prod DTM or Launch script with Dev or Staging script.

This can be done with the Adobe Cloud debugger under the "tools" tab or with a chrome addon like Requestly.

Avatar

Avatar

miikkal3149476

Avatar

miikkal3149476

miikkal3149476

14-03-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.

Avatar

Avatar

sfabri

Avatar

sfabri

sfabri

14-03-2019

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

We have not found a solution yet.

Avatar

Avatar

thomas_amsler

Avatar

thomas_amsler

thomas_amsler

11-03-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.

Avatar

Avatar

sfabri

Avatar

sfabri

sfabri

08-03-2019

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

Avatar

Avatar

thomas_amsler

Avatar

thomas_amsler

thomas_amsler

06-03-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.