SOLVED
Global Report Suite including mobile app data
1 Accepted Solution
Correct answer by
Ah, sorry, you would have your developers set the value.
So I often have a mix of values that are set by page (stuff like the category, the asset id, the title, etc... stuff that will be driven by the data and what is currently loaded.
The I will have stuff which is basically set and reused which is specific to the app itself... which app is it (we have three), the code version of the app and the build number (we don't force upgrades, so we need to know which version users are on - and while yes this is also sent in some of the standard metrics, having these pieces allow me to have a little more control), etc.
In your case, the report suite won't change in the middle of using the app, so your developers can set the value once, then attach it to all calls (or as I said, you could use Adobe Launch to just append this - which might be easier....)
The code base of your app will change the syntax of how the value is set and attached to the calls, so you may want your developers to check https://developer.adobe.com/client-sdks/documentation/ or https://aep-sdks.gitbook.io/docs/
Basically you would use something like:
MobileCore.track(state: "state name", data: ["key": "value"])
Where "key" would be "myapp.ReportSuite" and "value" would be "reportsuitea" or "reportsuiteb", etc
OR you can append it in your Launch like so:
{
"contextdata": {
"myapp.ReportSuite": "reportsuitea"
}
}
(set the context variable name "myapp.ReportSuite" to your naming convention, and the value "reportsuitea" to your report suite)
The rule trigger looks like:
Make sure to create a similar rule for actions as well as states, and maybe even for "Launch" events.
This will append your context variable to your server calls, and since the value of the report suite shouldn't be changing (unless you are using one Launch property to drive multiple suites - then this won't work)
Next, no matter of using processing rule....
In your reportsuite admin, General > Processing Rules
I like to check for app id (to make sure I don't accidentally target web traffic in the suite), you can add multiple conditions, then I choose to "overwrite" eVar5 with my context variable like so:
Make sure you test this first in a QA or Dev suite... processing rules will change the value of your dimensions, so you want to be sure the rules are working correctly before adding to prod... if something breaks there is no way to get the old values back.
Related Conversations
