Tuning
Last updated
Last updated
Tuning section includes:
In devtodev all paying users are divided into 5 segments by their payment amounts: minnows, dolphins, grand dolphins, whales and grand whales. These segments can be applied to the reports and dashboards and used as filters in order to analyze metrics of app performance for each user segment.
Also, such division might be helpful to see the distribution of your users by segments.
This page helps you specify payment intervals for each segment of users separately. Payments are measured in US dollars.
This section shows all the users that are marked as Cheaters or Testers. You can export a list of such users in a file and quickly unmark a selection of users.
Click on the pencil icon to open the configuration wizard. Here you can mark or unmark specific users.
Select the action you want to perform: mark or unmark the users.
Select the user identifier type: devtodev Id, Main Id, Advertising Id or User Id.
You can upload a CSV file with the list of identifiers. Or you can enter the necessary IDs in the text field using a comma as a separator.
In case you mark users as Cheaters (or Testers), after you click OK, the users will be tagged and their payments will be removed from the reports containing financial metrics.
Labels section allows you to manage time labels by adding marks on a timeline. These marks can be one-day or long-term events which can be specified as duration of in-game events, sales, update of app version, etc.
Labels can help you to monitor abnormal changes and identify the cause of it in a specific time period.
All specified labels can be presented in two ways:
Calendar view
Table view
You can create new labels by clicking “Add label” button in the top right corner. Each label can be customized using preset or your own categories.
By setting up alerts, you will always stay tuned and you will be able to monitor game metrics changes without getting into the system. You will be notified automatically in case of any changes in your main metrics, so you can act on them quickly.
This page will help you to set up alerts in 4 steps.
Specify a metric, its condition type and sensitivity.
Supported metrics: Active users, ARPPU, ARPU, Average number of custom events per user, Day 1 Retention (calendar), Day 7 Retention (calendar), Gross, New users, Number of custom events, Paying share, Paying users.
Condition types:
comparison with confidence interval (the previous day’s value will be compared to the confidence interval). You indicate the sensitivity parameter: high, medium, or low. This choice affects whether the confidence interval widens or narrows.
comparison with threshold (the previous day’s value will be compared to the specific value). You provide one or two threshold values for the metric: Upper threshold value and Lower threshold value.
сomparison with the previous day. You enter the percentage value by which the metric should change to trigger an alert, compare the value of the past day with the day before.
сomparison with the same day last week. You enter the percentage value by which the metric should change to trigger an alert, compare it with the same day of the last week (for example, Monday with Monday).
Customize preferable notification channels. You can choose to notify via e-mail, devtodev notification or Slack messages. It is important to add at least one addressee or webhook.
Choose notifications’ delivery time (based on Europe/Moscow time zone). You can customize the start date and decide whether alert campaign will expire or not on a particular date.
Give a name to your alert to be able to differentiate it from the other ones.
The Finish button will complete the configuration of your devtodev notifications.
In this section, you can rename the event and parameters without changing them in code. It will allow you to save time for bug fixing if there are some mistakes in naming.
Also, you can ‘block’ some events to stop collecting and storing their data. This functionality you can find in the “Tuning” section of the top menu, Integration subsection.
Please note, only space administrators or a space owner can edit custom events. The rest of the roles have only access to viewing. At the top of the report you can see the custom events overview:
Active custom events - events we are tracking and recording at the moment. These events are available for all reports.
Events blocked by customer - events which were implemented in the code but were blocked by the space administrator or space owner. We are not collecting and recording data for these events at the moment. You won’t be seeing these events when building reports.
Events blocked by system - events that were blocked by devtodev because of exceeding the limit by the number of tracked unique event names.
Under this overview block, you can see the list of active custom events.
You can do the following actions here:
Block the event to stop collecting its data
Rename the event
Rename the parameter of the event
When you rename the event, be attentive to the alias - it can’t repeat other aliases or event names. If you scroll down, you will see the list of blocked events which contains events that were blocked by the system or a customer. There is a limit of 300 unique event names that we can track simultaneously. If you reach the limit, you can block those active custom events that are currently irrelevant. To block or unblock the event you need to tap the lock icon.
We’ll start collecting data for this event only after it is unblocked.
Please note that you can unblock events from this list if you have less than 300 active custom events.
In this section, you can ‘block’ certain user properties to stop collecting and storing their data. You can find this functionality in the “Tuning” section of the top menu, under the “Integration” subsection.
Please note that only space administrators or a space owner can edit custom properties. Other roles have only access for viewing. At the top of the report, you can see the overview of user properties:
Active custom user properties - properties we are currently tracking and recording. These properties are available for all reports.
Properties blocked by customer or system - properties that were implemented in the code but were blocked by the space administrator or space owner. We are not collecting or recording data for these properties at the moment. You won't see these properties when building reports.
There is a limit of 30 unique property names that we can track simultaneously. If you reach the limit, you can block those active custom properties that are currently irrelevant.
To block or unblock multiple properties, you can mark the checkboxes and then click on the lock icon.
We'll start collecting data for this property only after it is unblocked.
Please note that you can unblock a property from the blocked list if you have fewer than 30 active custom properties.
In order to provide you with the correct data in the reports and make them insightful for you, we will keep you informed about different errors and issues in the data such as achieving the events or parameters limit and errors connected to the integration or tracked data. These notifications could contain information about the following issues:
transactions exceed the limit by the amount of payment;
events with the same name but different register are tracked;
number of currency types are about to reach the limit;
some transactions are doubled;
and more.
Notifications about errors and different warnings are displayed in the Notification section in the right upper corner.
More details about each of them are available under the “Read more” button. After you tap it, you will be redirected to the “System alerts” sections where you can find the following:
list of all errors and warnings of the current application version;
a detailed description of the errors and documentation links with information about the limits and integration best practices.
You can also postpone the notifications for 7 days by using the "Remind later" button in the Notification section. After 7 days we resume sending notifications if the error or the warning persists.
By default, error notifications are sent to users with owner or admin rights. They can subscribe to notifications users with different permissions or unsubscribe them. To do this, at the top of the System alerts page in the Tuning - Integration section you need to click on the pencil icon, select a user from the list and click Apply:
The Raw Export section allows you to build custom reports and download them as csv. files. This may be needed if you want to work with data on your own and build more complex and customized reports.
To create a new report, click the "Add a new report" button above the table and follow the instructions.
Choose events and data
Select time frame for the report
Name your report
To download an existing report, find it in the table and click "Download" in the right column of the table. The report will be downloaded to your computer.
You can download the reports with only "Ready" status. If a report is in a "In progress" status, wait until it reaches 100%. If the report is in an "Empty report" status, it means that there is no relevant data to be exported.
After the report is created, you can see its settings by clicking the button in the “Settings” column.
Please note that reports will be available for downloading only during 14 days after their creation.
You can find description of each event table in this section.
Export your cohorts to Google Ads and Facebook to use the audiences for ad targeting. To start the integration, open Settings → 3rd party sources → Cohort export.
Use the following reports to export audiences:
‘Segments’: select one dynamic or some static segments, and click ‘Export cohort to Ad network’ in the top right corner.
‘SQL’: get a list of user IDs as a result of your query. Click the sandwich icon in the top right corner and select ‘Export cohort to Ad network’ to export the cohort to your ad account.
‘Users’: filter users by parameters, properties, completed events, then click the sandwich icon in the top right corner and select ‘Export cohort to Ad network’.
‘Paying status prediction’ report: select a segment with a certain purchase probability and click the Export cohort button.
‘RFM’ report: select the desired segment, e.g. Champions - the users who pay often and a lot, and click the Export cohort button.
’Funnels’ report: build a funnel and export the audience who completed specified steps by clicking ‘Cohort export’ in the dropdown menu.
1) After you have prepared an audience to export and clicked ‘Export cohort to Ad network’ in the new window, you need to choose whether you want to add new users to an existing audience in your ad account or build a new one. To create a new cohort, enter the name to be displayed in the ad network account.
2) Next, you need to name the cohort to be exported. This name is displayed in devtodev in the list of all exported cohorts. This is needed for history displaying and cohort management.
If your cohort was created from a dynamic segment, then on the next step, you will need to select the type of cohort synchronization: daily (the audience gets exported every 24 hours) or one-time. If you choose daily synchronization, then uses will accumulate in the cohort and the users who left the dynamic segment will not be removed from the cohort.
3) Click ‘Apply’ to finish audience export. Audience creation can take up to 12 hours to fully complete. You can find the cohort synchronization status in the Exported cohorts section.
The ‘Cohort export’ section contains information about exported cohorts - their names, ad networks where the cohort was exported to, date of the last synchronization, audience size, cohort state: synchronization, was it exported or an error was returned, audience type: one-time export or daily export, as well as buttons to stop syncing daily cohorts.
