What are possible reasons why ClearVariable fails? | Community
Skip to main content
T
thomas_amsler
New Participant
February 21, 2019
Solved

What are possible reasons why ClearVariable fails?

  • February 21, 2019
  • 34 replies
  • 31626 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

    Show previous replies
    Jennifer_Kunz
    Jennifer_Kunz
    New Participant
    March 18, 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.

    S
    sfabri
    New Participant
    March 14, 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 ".

    miikkal3149476
    miikkal3149476
    New Participant
    March 14, 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.

    S
    sfabri
    New Participant
    March 14, 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.

    miikkal3149476
    miikkal3149476
    New Participant
    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.

    S
    sfabri
    New Participant
    March 14, 2019

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

    We have not found a solution yet.

    T
    thomas_amslerAuthor
    New Participant
    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.

    S
    sfabri
    New Participant
    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 :-) )

    T
    thomas_amslerAuthor
    New Participant
    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.

    T
    thomas_amslerAuthor
    New Participant
    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.

    Show more replies
    Terms & ConditionsAccessibility statement

    Loading footer...