AEP Web SDK - Tracking Merchandising Variable & Events

[satyanarayanam1]

Hi Team,

We are using Web SDK to migrate to AEP, could you please share some samples on tracking merchandising variables and events using Web SDK into AEP & Adobe analytics, do we need to add processing rules for these merch-vars as well to get them tracked into analytics?

We tried using Adobe Analytics Template mixin but no luck. Any help would be much appreciated. Thanks..!

[Beenit_Chatterjee]

Fyi..

There's an "Adobe Analytics ExperienceEvent Template" field group within XDM schema which has all the required field to track Analytics data. This template does have field to populate merchandising evar or any event which you would like to pass within productListitems.

Cheers!

[satyanarayanam1]

This mapping works for AEP platform, for the analytics variables s.products mapping this currently doesn't support. Product engineering teams are working on this to automap merchvars & events. We need to await for the release or for the interim you can use blackbird API to achieve the same.

[VT]

It's been over a year since this comment. 

Has there been any movement on this yet?

[yuhuisg]

Yes, you can make use of automatic mapping of variables between your XDM object and AA's merchandising-related variables and success events. I don't recall Adobe making a big announcement about this, but the feature has been around for about a year already.

See this help page for the list of all automatically mapped variables: https://experienceleague.adobe.com/docs/analytics/implementation/aep-edge/variable-mapping.html?lang.... In particular, take note of the ones for "productListItems[]".

[satyanarayanam1]

@VT  - Yes, now the Web SDK does support automatic mapping for products and merchvars when you follow the structure as represented in the Adobe Analytics Template Field Group (In the screen-print in above comments).

[hs_vk]

Hi @yuhuisg @satyanarayanam1 @Beenit_Chatterjee 

Thanks for answering this question. Would appreciate if you could please clarify this-

To send data to (or to use without any mapping) the Cart Additions, Cart Removals, Product Views (OOTB/standard AA metrics) - do we need to use the Commerce details field group i.e. productListItems and its respective fields like commerce.productListAdds.value?

However, if we use the Adobe Analytics Template Field Group just by itself(_experience.analytics.customDimensions.eVars.eVar1) or within the productListItems (i.e. productListItems[]._experience.analytics.customDimensions.eVars.eVar1), we won't be able to auto-map specific evar/props/events to the given metrics (Cart Additions, Cart Removals, Product Views), is that right?

Thanks

[yuhuisg]

@hs_vk ,

---

@hs_vk wrote:

To send data to (or to use without any mapping) the Cart Additions, Cart Removals, Product Views (OOTB/standard AA metrics) - do we need to use the Commerce details field group i.e. productListItems and its respective fields like commerce.productListAdds.value?

---

Think of it this way:

The "productListItems" field group is used to build the equivalent of AA's s.products string. So you will definitely need to set this productListItems whenever you want to track products for any ecommerce step.

Separately, the "commerce" field group is used to track the equivalent of AA's ecommerce success events, e.g. scAdd, scRemove, etc. Referring to the documentation on mapped variables https://experienceleague.adobe.com/docs/analytics/implementation/aep-edge/variable-mapping.html?lang..., you can see that you need to set the commerce fields to count your success events properly. E.g. where you would have set "scAdd" in your AA implementation, you will need to set "commerce.productListAdds.value" = 1.

---

@hs_vk wrote:

However, if we use the Adobe Analytics Template Field Group just by itself(_experience.analytics.customDimensions.eVars.eVar1) or within the productListItems (i.e. productListItems[]._experience.analytics.customDimensions.eVars.eVar1), we won't be able to auto-map specific evar/props/events to the given metrics (Cart Additions, Cart Removals, Product Views), is that right?

---

If you set productListItems[]._experience.analytics.customDimensions.eVars.eVar1, then you're setting the equivalent of a Merchandising eVar1 in your s.products string. And recalling how Merchandising eVars work, then those eVars would be able to reported with your given metrics properly.