AEP web sdk consider and counts s.tl call as pageview & Duplicate pageview metrics | Community
Skip to main content
DhanA2
DhanA2
Level 3
November 12, 2022
Solved

AEP web sdk consider and counts s.tl call as pageview & Duplicate pageview metrics

  • November 12, 2022
  • 2 replies
  • 7377 views

Hi Team,

Doubt on AEP SDK IMPLEMENTATION:

I have two xdm send events

1. For pageload and

2nd one for Interactions/link click
My problem is: my link clicks got counted as page view it causing 2 pageviews.
I do have proper setup on web details class in schema value of pageview 1 and link click 0 for pageload event.
Links click 1 and pageview 0 for link click event. Not sure why link clicks incrementing pageviews. Anyone can help me on this

 

Note: Custom events are working proper it have exact pageview count but out of the box pageview metrics double counted.

 

 

Best answer by yuhuisg

There was some discussion about this in another forum, and this was the consensual solution:

---
For AA alone, forget eventType, setting web.webPageDetails.pageView.Value=1 or web.webInteraction.linkClick=1 themselves don't decide if the call would be s.t or s.tl(). Following is how AA processing works wrt. page vs non-page call:
  1. For a beacon to be considered a page view in AA you need either:
    • webPageDetails.name, Or
    • webPageDetails.URL
  2. For a beacon to be considered a link in AA you need:
    • webInteraction.type, And
    • Either of below two:
      • webInteraction.name, Or
      • webInteraction.URL
For Adobe Analytics you don't need, webPageDetailsvalue=1 for a page view or webInteractionValue=1 for a link click. However, doing this is definitely a good practice since you do need these for CJA and RTCDP.
---
Credit to Rajdeep Singh for this.

2 replies

PratheepArunRaj
Community Advisor and Adobe Champion
PratheepArunRajCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
November 12, 2022

Dear DhanA2,

Page Views are not just based on the Schema Value with Page View equals 1 or Link Click equals 1, but only based on the event type.

Set the page views properly like the one below.

Page View Call:

Non-Page View Call (i.e. Link Clicks):

So, set the Event Type properly, it will be resolved.

Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics

Thank You, Pratheep Arun Raj B (Arun) | Xerago | Terryn Winter Analytics
DhanA2
DhanA2Author
Level 3
November 13, 2022

Hi @pratheeparunraj ,

 

Thanks for your response in my case event type also set as you mentioned but still I'm getting two pageviews, Do I need to focus on any other configs?

 

FYR:

Thanks for you help

 

 

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
November 13, 2022

I haven't used the Web SDK, but I initially had a similar issue with the Mobile SDK... make sure that neither PageName or Page URL is being set on your actions... if either of these dimensions is set (via processing rules, or maybe being sent as part of the action) this will count as a page view

 

I have a few hit level eVars to hold the page name and URL on all hits (page views and actions) to store this info (it also allows me to have 255 character limit, as opposed to PageName's 100 character limit)

yuhuisg
Community Advisor
yuhuisgCommunity AdvisorAccepted solution
Community Advisor
June 28, 2024

There was some discussion about this in another forum, and this was the consensual solution:

---
For AA alone, forget eventType, setting web.webPageDetails.pageView.Value=1 or web.webInteraction.linkClick=1 themselves don't decide if the call would be s.t or s.tl(). Following is how AA processing works wrt. page vs non-page call:
  1. For a beacon to be considered a page view in AA you need either:
    • webPageDetails.name, Or
    • webPageDetails.URL
  2. For a beacon to be considered a link in AA you need:
    • webInteraction.type, And
    • Either of below two:
      • webInteraction.name, Or
      • webInteraction.URL
For Adobe Analytics you don't need, webPageDetailsvalue=1 for a page view or webInteractionValue=1 for a link click. However, doing this is definitely a good practice since you do need these for CJA and RTCDP.
---
Credit to Rajdeep Singh for this.
    S
    sumit_nijhawan
    Level 2
    August 13, 2024

    All above solutions did not work for me too. Then we inspected settings in  Adobe Experience Platform Web SDK extension.

    Check if you have enabled click data collection.

    if Yes, when sending event data, dont automatically include default context information and rather, select "Specific context information".

    And disable Web (information about current page).

     

    Enabling information about current page will send webURL by default on each custom linkclick and thus increase the pageview because of below condition.

     

    1. For a beacon to be considered a page view in AA you need either:
      • webPageDetails.name, Or
      • webPageDetails.URL
    yuhuisg
    Community Advisor
    yuhuisgCommunity Advisor
    Community Advisor
    August 14, 2024

    Interesting! This might be a bug in the extension that Adobe could investigate. You could open a new issue in the extension's Github page https://github.com/adobe/reactor-extension-alloy/issues, or you can raise this with Customer Care and let them bring it to Adobe Engineering's attenion.

    Terms & ConditionsAccessibility statement

    Loading footer...