Skip to main content
MMP: Store App Details Page
Updated over a year ago

Store App Details Page

The Store App Details Page provides in-depth analytics on the performance of your app on a specific store. Provide you with widgets for important metrics, a customizable performance chart, a paid vs. organic graph, and details on all the campaigns set up for this app. Let's go through each section.

Store App Name, ID & Edit

Name & ID

At the top of the page, you will see the name of the app and the store id for iOS or Android

Edit

On the right side, you have the Edit button.

Allowing you to quickly adjust information about the app like the App Store, Icon, Description, and more.

📌 Synchronize with Store Details

If you click on the above option after providing the Store ID, then it will auto-fill all the app details like Name, Icon, Store URL, Description, and Screenshots for you by referring from the respective store.

Quick Links

Quick Links will take you to either the Explorer Report with the specific app you are on automatically filtered or the Audits page to see a timeline of any changes made by any user/system in Swaarm for this app.

The 6 Widgets

At the top of the page, you have six widgets displaying valuable metrics for your app's performance. Each widget displays Today, Yesterday, and MTD (Month to date) statistics. The numbers are a total of both Paid (green) and organic (blue) users, which can be shown by hovering over the blue and green bars.

💡Widget Tip

Clicking on any of the Today, Yesterday, or MTD rows will take you to a Custom Report with the dimensions and metrics automatically filled out for you. Take this even further by adding additional dimensions/metrics to create an even more advanced detailed report.

Widget Descriptions

  • Active Users - Number of unique active users

  • New Users - Number of new installs including both organic and paid users

  • ROAS - Return On Ad Spend

  • Revenue - Revenue generated via in-app purchases

  • Costs - Payment to your Partners

  • ARPU - Average Revenue Per User

Performance Chart

The Performance Chart provides a visual guide to your app's progress, helping you determine the necessary steps to attract new users and advance further. Turn on and off metrics by selecting them at the bottom of the chart.

Hover over the chart to see data points for that time.

Time Granularity

To get a bigger picture or even a more detailed analysis, change up the report by selecting a different time granularity between Hours, Daily, Weekly, or Monthly.

Show Deltas

Turning on Show Deltas will give you a comparison (depending on the time granularity you select) of Today vs. Yesterday or the current month vs. the previous month.


Paid vs. Organic Graph

Even with the brief overview that the 6 widgets provide, sometimes a different view can help make better data-driven decisions. With the Paid vs. Organic graph, you can select any of the 6 widget metrics, as well as event analysis. This graph will give you a good overview of paid and organic user acquisition and performance.


Offers/Campaigns

After viewing the details of how your app is performing with the above charts and graphs, you can then utilize the bottom section to see individual campaign setup and performance.

Offers Tab

Here on the Offers Tab, you can see the list of campaigns set for your app and their performance metrics. Clicking on any of the offer names will take you to the Offer details page. If you want to view the data outside of Swaarm, you can click Download CSV.

Filters

  • Range

    • Select the time range to see the metrics below

  • Granularity

    • Choose to view data on a Day or Month basis

  • Metrics

    • Add or remove metrics from the table below

  • Search

    • Find a campaign by name or offer an ID

  • Status

    • Filter out offers based on their active status


Tokens Tab

This security token ensures the authenticity of events sent by your SDK. The token will be automatically generated and then your developer will configure this token in your app while integrating the SDK. Its primary function is to verify that the events originate from your app, and it's mandatory to configure a token for every store app.

Test Token

You have the option to designate the token as a Test token. The test token is specifically designed for testing events after the SDK has been integrated. This ensures that all related logs and information are conveniently accessible within the SDK debug report, streamlining the testing process.

When you mark the token as Test, any event generated using the token will only appear in the SDK Debug Report and will not be reflected in the platform's data.


Breakpoints Tab

Conventionally, the app developer writes code to send events. However, when the app undergoes updates with new UI or features, it can take weeks to publish the changes on the app store. Additionally, it may take some time for users to update their devices, resulting in potential data loss during this transition period.

To address this issue, we have developed code-less tracking via Breakpoints. It's a unique feature that requires no code modification to send events using the SDK.

✏️Before Using Breakpoints

The prerequisite for using Breakpoints is that the SDK must be configured within the app.

To set up breakpoints, you need to have the app installed on your device and the Vendor ID which is a unique identifier that is assigned to an app on a device.

After that, you need to follow these steps,

  1. Go to Organization > Settings > Breakpoints tab, and insert the Vendor ID (IDFV)

  2. Open the app on the same device associated with the Vendor ID(IDFV), and navigate through each screen following the user flow

  3. Switch back to the Breakpoints tab on the Store App Details page, and you will see all the screen captures start reflecting on the tab as app pages

  4. Now, you can decide from here, which event to map on which app page. For example, the main calculator page is mapped to the 'someone did a calculation' event above

  5. You need to click on 'Track Breakpoint' below the screen capture and select an event

  6. And your event mapping is done, now you're all set to track events!

Now, whenever the user lands on that page and performs any activity on that page, for example, performing a calculation above, the mapped event will be tracked into the platform.

And, in case you want to untrack the event on the respective page due to some reason, then just click on the 'Untrack Event', and event tracking will be stopped on that page.

Common Use Case

Whenever there's an update in the app where the UI is revamped or new features are added and if it needs to be updated on the event tracking side as well, then you can follow the above process to set up breakpoints and start tracking events without having to rely on code updates for event-tracking and configure tracking directly on the platform.

Did this answer your question?