Cannot set s.products using mobileSDK contextData? | Community
Skip to main content
Level 2
September 23, 2024
Question

Cannot set s.products using mobileSDK contextData?

  • September 23, 2024
  • 1 reply
  • 557 views

I notice from this page https://experienceleague.adobe.com/en/docs/analytics/admin/admin-tools/manage-report-suites/edit-report-suite/report-suite-general/c-processing-rules/c-processing-rules-configuration/processing-rule-dimensions that s.products cannot be set via Processing Rules.

Does this mean it is impossible to set s.products from a mobile app using processing rules to map contextData to Analytics variables? If not, how do you do it?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
September 24, 2024

Hi, 

 

If you are using XDM Streams you can set it.. but if you are using the old ACP SDK, and setting data using context variables and mapping, s.products actually has to be sent through the request directly using &&products=[entire formatted products string], and if you are passing events with your products (since you can't really read the events from the products string, you can pass those specific events using &&events=[events list]

 

Obviously Adobe is pushing people towards using XDM Streams, so if you are starting out, you should definitely go that route, even if you plan on using the XDM Stream a.tags (direct to AA schemas), you should be able to map to s.products schema.... 

Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
September 24, 2024

I should add, I haven't switched to XDM Streams yet, but like passing products directly in the old ACP method, you should be able to pass the products string (without needing to map it using processing rules).

 

Technically, you should be able to set ALL your values directly into the XDM Stream without having to use processing rules for that matter...  but if you are trying to transition from ACP to AEP, and you are trying to reduce the number of changes all at once, you can keep your context variables / processing rules... but if you are starting new, I would personally skip the processing rules if you can.. that interface is a bit dated and hard to use.