In this exciting release, we’ve done a lot of work around primary metrics to make sure you have the right measures available to validate or disprove your targeting activities.

We’ve also optimized our Android and iOS SDKs by adding hibernation mode, so they reduce battery and CPU consumption. Read on for details about both.

Release | Primary success metric

On mtribes, a primary metric is used to measure the success rate of Scenario activity. The primary metric is set during the Experience template build. Activity is then tracked, and data displayed accordingly on your Scenario page.

To give you even more control and visibility over how your Scenarios are performing compared to others, we’ve released the following changes and updates:

Scenarios | New Traffic (30 days) metric

We’ve added a new metric called Traffic (30 days) to the Scenario page. This metric displays the specific Scenario count against all Scenarios served, and the success rate as a percentage. This allows you to identify how your Scenario is performing at a glance.

An mtribes Scenario page open showing the served count and success rate.

Experience | New primary metric dropdown

We’ve implemented a Primary metric dropdown menu on the Experience template. You can select a primary metric from a range of metrics and active event types and set this as the default measure for comparing Scenario performance. The view can be temporarily changed on the Scenario side, so schedulers can use another metric to compare activity, but this will revert to the (default) primary metric view once closed.

An mtribes Experience template showing properties, with the primary metric open.

Experience | New custom primary metric feature

You now also have the option to define your own primary metric from a custom event type. The custom metric feature is accessed through the Primary metric dropdown menu when setting up your Experience template. Once clicked, a modal opens on screen that prompts you to enter an Event type. This custom metric can then be set as your new primary metric for measuring Scenario success, and can be edited through the same menu.

An mtribes Experience template with the edit custom metric modal open.

Release | Hibernation mode for Android and iOS SDKs

Apps can sometimes consume battery quickly or use up too much CPU on your device. To prevent this from happening with mtribes, we’ve added hibernation mode to our Android and iOS SDKs, to optimize how Experiences are served, or analytic events captured across these devices.   

An illustration showing how hibernation mode works with Android and iOS SDKs.

Note: Hibernation mode is available in Browser SDK since v1.0.0-beta.8.

This means that when you use an app with an mtribes SDK, and it goes to the background for 2 minutes, the SDK will go into hibernation mode. This reduces battery and CPU consumption. Once the app comes back to the foreground, it will re-establish connection with our backend services. 

A small but powerful add, because if you’re happy, we’re happy. 


| For more info, browse the Help Center, or leave us a message on the chat widget.

Did this answer your question?