Unspecified Values Increase | Post webSDK migration due to Adobe Target calls | Community
Skip to main content
S
SravaniRa1
February 18, 2025
Solved

Unspecified Values Increase | Post webSDK migration due to Adobe Target calls

  • February 18, 2025
  • 1 reply
  • 675 views

Hi Team,

We've migrated to webSDK and sending data to Adobe Analytics. Adobe Target also implemented through webSDK.

While sending data to Edge Network, Adobe Target "decision proposition" call triggers prior to "Analytics page load" call. The decision proposition call has some "data object" analytics attributes append which implemented in "webSDK extension" and this Target call is reaching Adobe Analytics.

Issue - Post webSDK migration, the eVar "unspecified" values spiked up for the Page load related metrics(unique visitors visits, and page views).
We've reached Adobe Team and they concluded due to "Adobe Target decision proposition call" reaching Analytics we are seeing spike in "unspecified" values count. To avoid that situation the Adobe Team hasn't suggested any solution to us.

How to make sure the "unspecified" values for the Pageload metrics are not spiking due to Target, any solutions or suggestions.

Thanks 





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 bjoern__koth

Hi @sravanira1 

in your send event action, you can use guided events that should make sure that the request only ends up on either target or analytics.

https://experienceleague.adobe.com/en/docs/experience-platform/tags/extensions/client/web-sdk/action-types

 

These guided events should make sure that payload fields that implicitly end up in Adobe Analytics are dropped.

 

Ultimately, your devs must/should make sure that the calls contain only the data that is meant to be part of the call.
For the data part you mention, they could for instance take two different Web SDK "Variable" Data Elements, one for Target and one for Analytics.
And in the request to target make sure to choose the Target-only Variable Data Element.

 

1 reply

bjoern__koth
Community Advisor and Adobe Champion
bjoern__kothCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
February 18, 2025

Hi @sravanira1 

in your send event action, you can use guided events that should make sure that the request only ends up on either target or analytics.

https://experienceleague.adobe.com/en/docs/experience-platform/tags/extensions/client/web-sdk/action-types

 

These guided events should make sure that payload fields that implicitly end up in Adobe Analytics are dropped.

 

Ultimately, your devs must/should make sure that the calls contain only the data that is meant to be part of the call.
For the data part you mention, they could for instance take two different Web SDK "Variable" Data Elements, one for Target and one for Analytics.
And in the request to target make sure to choose the Target-only Variable Data Element.

 

Cheers from Switzerland!
    S
    SravaniRa1Author
    February 19, 2025

    Thanks for the response. Please find the below configurations of the Target rule
    Events - Adobe Experience Platform - send event complete
    Actions -> 

    1) AEP webSDK -> Apply Propositions

    2) AEP Platform WebSDK -> Send Event -> decision proposition display type(no Data variable used)

    Still this call is reaching analytics because we have some variables configurations under "WebSDK Extension" and causing spike in "unspecified" values of eVars.

     

    Enabling the "guided events" and selecting "Request Personalization" makes the call to get drop from not reaching Analytics and the "unspecified" spike in eVars would get sorted?
    Please confirm.

    Thanks

    Sukrity_Wadhwa
    Community Manager
    Sukrity_WadhwaCommunity Manager
    Community Manager
    February 28, 2025

    Hi @bjoern__koth,

    Can you please help @sravanira1 further with their query?

    Thanks!

    Sukrity Wadhwa
    Terms & ConditionsAccessibility statement

    Loading footer...