Mobile App Journey Report

Overview

The mobile App Journey report shows the results of your mobile journey. You’ll be able to see how actions performed within your app, confirm SDR implementation by using rules, and where any failures may have occurred.

Click on an app journey card to open its report. The journey must have run at least once to see any results. If it has not yet run, the progress bar will show.

Report Screen

The report shows a thumbnail image for each step of the test and four categories of results in their respective tabs: Action, Tags, Compliance Rules, and Request Logs (see the tab descriptions below).

View the results of each step in the test and determine whether or not it executed properly and to help you troubleshoot any failures. This can expose data governance lapses, navigational problems with the journey, or unrecognized tags. Even if all the steps in the test have executed correctly, it may still be useful to access the Request Log Tab in this report to find what external resources are loading and if any of them are tags that should be validated.

Begin by visually scanning the thumbnails, which will have a green check mark to show success or an alert icon indicating an action or rule failed. Click the thumbnails to see details on each step. All steps defined in the journey may not appear here because some may depend on a previous step. If the previous step fails, the test may be prevented from showing subsequent steps or they may not run correctly.

Next, look at each step and check the four tabs for a status showing a failure or other insights. If a step shows a failure, one of the tabs will have a corresponding alert icon:

Action

This shows the Actions in each step. If there is a failure on this tab, visually inspect the action to ensure that step can actually execute on that screen.

The screenshot is taken just before the next step executes, which lets you see the final state of the step. Each screen is the result of the step from the previous screen.

Tags

All tags discovered on this step appear here. Click a tag to view the data sent from this screen so you can set up rules for validation. You can set up rules on-the-fly from this tab (see Creating Rules in Journey Reports in Help).

Rules

If you have chosen one or more rules, this tab shows which ones have passed or failed for this step. If a rule has failed, check to see if 1) the app is configured to send the tag or 2) your rule is set up correctly by checking against the data in the Tags tab. An error on this screen may show either the tag failed to load or data in one or more variables is configured incorrectly. The journey will continue to run even if a rule fails. You can set up rules on-the-fly from this tab (see Creating Rules in Journey Reports in Help).

Request Log

The Request Log tab shows all the external web calls from that step so that you can verify that the app is accessing the correct content. The list of URLs can also help you to discover additional tags of which the test is unaware. If you encounter a tag here that ObservePoint should validate, contact your data governance consultant.

Journey Rules

Journey rules can execute at any time during the journey. This is especially helpful for catching batched image request from the app. The journey rule is successful if it executes at least once during the journey.

Next Steps

Resolve any failures in the journey by either fixing the step or compliance rule and re-running it. If you discover code problems in the app, upload a new version of the app after making corrections and apply the journey to it.

Troubleshooting Tip: If the AppAssurance app returns no tags or network requests after a completed run, then this is likely due to the app not being an X86 build. Non-X86 builds i.e. ARM builds are designed to default to a beta test version of the device, thus it is not synced to a proxy and no traffic is displayed. Build an emulator with X86 architecture to see the tags and network requests.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.