Link Clicks Tracking & Storing the values in a page level - Intermittent issue | Community
Skip to main content
R
RoystonPr
Level 3
June 29, 2021
Solved

Link Clicks Tracking & Storing the values in a page level - Intermittent issue

  • June 29, 2021
  • 3 replies
  • 1552 views

Hi Team,

 

We have one rule to capture link dynamic text values/urls and their clicks for one page in the website.

 

Events : Library Loaded Page Top

Action: Setvariables > In the custom code - open editor, we are storing the two evars with click function and capturing two events.

 

Click ID: a#example (number of clicks along with text and url values)

s.eVar1 = example
s.eVar2 = www.example.com
s.events = event 1

s.tl call

 

Click ID: a#example1 (only number of clicks we are storing here)

s.events = event 2

s.tl call

 

Scenario: A page has 2 links to capture along with their dynamic text values/dynamic urls and their click events.

 

All these configuration working fine and storing the values/clicks properly for sometime in a day. Sometime its not working properly.

 

We have published the build one month back. After publishing, rule was ok. Recently we are seeing these type of intermittent issue.

 

For the particular page, page view image request call is coming up fine all time but only clicks are not capturing for sometime in a day. Are we missing anything ?

 

Any idea on this?

 

Regards,

Shane

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 yuhuisg

If your clicks cause the browser to navigate to a new page, then yes, you will face the issue of some hits not being collected. This is because there's a "race condition" between your Custom Link hits being sent vs the browser redirecting to that next page. Whichever finishes first "wins". So in some situations, it is entirely possible that the browser has begun redirecting before your Custom Link hits have been sent successfully.

3 replies

V
Adobe Employee
vidurb80577666Adobe Employee
Adobe Employee
June 29, 2021

@roystonpr 

It is recommended to set linkTrackVars and linkTrackEvents using custom code if you set variables in Launch using the custom code editor for s.tl call.

Please refer the links below:
https://experienceleague.adobe.com/docs/analytics/implementation/vars/config-vars/linktrackvars.html?lang=en

https://experienceleague.adobe.com/docs/analytics/implementation/vars/config-vars/linktrackevents.html?lang=en

 

Also please check if the rule you have created getting fired every time someone clicks on those links. If not, no server call will be generated and data will not be captured. 

    R
    RoystonPrAuthor
    Level 3
    June 30, 2021
    @vidurb80577666: I have done setting linkTrackVars and linkTrackEvents. Server call is coming up for sometime when clicks and not coming for sometime in a day. Its quite strange. "Other Click" request is coming anyway when clicks. But only sometime in a day as mentioned above.
    yuhuisg
    Community Advisor
    yuhuisgCommunity AdvisorAccepted solution
    Community Advisor
    July 2, 2021

    If your clicks cause the browser to navigate to a new page, then yes, you will face the issue of some hits not being collected. This is because there's a "race condition" between your Custom Link hits being sent vs the browser redirecting to that next page. Whichever finishes first "wins". So in some situations, it is entirely possible that the browser has begun redirecting before your Custom Link hits have been sent successfully.

      R
      RoystonPrAuthor
      Level 3
      July 2, 2021
      @yuhuisg Got it mate. Any permanent solution for this?
      jantzen_b
      Adobe Employee
      jantzen_bAdobe Employee
      Adobe Employee
      July 20, 2021
      Do any of the answers below answer your initial question? If so, can you select one of them as the correct answer? If none of the answers already provided answer your question, can you provide additional information to better help the community solve your question?
      Terms & ConditionsAccessibility statement

      Loading footer...