Websdk Migration

[bindukumari90]

Hi Team,

Currently we have three different rules on page load i.e.  one rule sending data to AEP, in that we are setting some eVars , one target rule and other analytics rule through websdk. All these rules are using different schema, but all these rules are causing inflation in the analytics pageviews.

So, Is there any solution to reduce  the pageviews.

Thanks!!

[bjoern__koth]

This is an old issue, you may want to have a look at the new "Guided Events" in the sendEvent action.

https://experienceleague.adobe.com/en/docs/platform-learn/implement-web-sdk/applications-setup/setup...

These should address the issue you are reporting.

For a better understanding, check the documentation

https://experienceleague.adobe.com/en/docs/analytics/implementation/aep-edge/overview

=> "How Adobe Analytics handles Edge Network data"

I think this highlighted part may be your issue: if you set the web.webPageDetails.name or .URL, it will implicitly always end up on Adobe Analytics side, even if it is a propositionDisplay event meant for Target.

And also a gist on GitHub with a patch the you could implement before guided events, essentually setting a "webInteraction.type" for non-page view events.

https://gist.github.com/jfkhoury/b390688267854c75d75245ed0c12253b

Hope that helps

P.S. here's also an old thread from the beginning of AEP when this was detected. It just took Adobe 2+ years to fix and update their documentation xD

[bindukumari90]

Thanks @bjoern__koth But this will resolve only target pageviews, what we can do if we are sending data to AEP and it's pageview is also going into analytics.

[bjoern__koth · Accepted solution]

I would says not if you leave the web.webPageDetails part empty.

Maybe worth checking the XDM payload in your requests (filter for "/ee")

UPDATE: I would also check if you can see any requests in Assurance that indicate the request is ending up in Analytics

[bindukumari90]

Okay, thanks!!