Mapping variables (evars and props) in AEP sdk5 | Community
Skip to main content
rupaljain2408
rupaljain2408
Level 3
September 16, 2019
Solved

Mapping variables (evars and props) in AEP sdk5

  • September 16, 2019
  • 3 replies
  • 4996 views

Hi All,

Which is the best way to map evars and props while using AEP SDK for mobile app analytics :

1) Map using Mobile services UI, which will create processing rules at report suite leve. For this we need to create two property in Mobile services , as only one report suite can be attached with one property in Mobile services.

2) Map by creating processing rules at report suite level directly.

Which is the best and feasible way to map variables? Please suggest.

Thank you

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 rupaljain2408

Hi praschetan​,

Thank you for your response, even I feel that MS UI is easier to use and it creates the processing rules at report suite. However, my confusion is that MS app is attached to only one report suite, so we will have to create two apps (one for dev and one for prod report suite) . But we can only attach one app in Launch MS extension. How to handle that scenario? Should I be attaching production MS app while moving into production and keep dev app for dev library ? Isnt it a manual process then.

Please let me know if you know any another approach on using MS UI.

3 replies

cprasad
Adobe Employee
cprasadAdobe Employee
Adobe Employee
September 16, 2019

Processing rules to map variables and metrics are always applied to a report suite. Mobile Services UI and Processing Rules UI (within Adobe Analytics) use the same APIs to manage rules for a given report suite.

As you point out, using Mobile Services UI requires extra steps - however, for some users, the MS UI may be easier to use. You may accomplish mapping in either of the two UIs you find comfortable.

    rupaljain2408
    rupaljain2408AuthorAccepted solution
    Level 3
    September 17, 2019

    Hi praschetan​,

    Thank you for your response, even I feel that MS UI is easier to use and it creates the processing rules at report suite. However, my confusion is that MS app is attached to only one report suite, so we will have to create two apps (one for dev and one for prod report suite) . But we can only attach one app in Launch MS extension. How to handle that scenario? Should I be attaching production MS app while moving into production and keep dev app for dev library ? Isnt it a manual process then.

    Please let me know if you know any another approach on using MS UI.

      cprasad
      Adobe Employee
      cprasadAdobe Employee
      Adobe Employee
      September 17, 2019

      The Mobile Services extension is only required if using one or more of the following features: in-app messaging, push, acquisition, and location points of interest management.

      If you are using the features listed above, you'll need to create separate apps in Mobile Services and separate properties in Launch (as you can only have one environment per Mobile Services extension).

      If you are not using the features above and are looking, solely, to setup Adobe Analytics reporting, then you may setup multiple apps in Mobile Services (or configure report suites and processing rules in Adobe Analytics) - then, in Launch with only a single property (as you won't need the Mobile Services extension)...you'll configure the Adobe Analytics extension with all the report suites you want per environment.

        Terms & ConditionsAccessibility statement

        Loading footer...