This guide will help you navigate through our demo, and understand how you can use these reports when you activate your own payment analytics in Publisher Account. Below is information on how to read the dashboards, description of each of their contents, definitions for the different metrics and dimensions, and a list of FAQ. If you have any further questions, ask us to clarify at email@example.com!
A dashboard is a collection of charts and graphs that give you insights into a specific topic. Each one will allow you to increase awareness on a different part of your company and help you make data-driven decisions.
Each dashboard has several filters, located at the top, to allow you to filter your data through the many dimensions. To utilize these filters, select one and check the boxes of the dimensions through which you would like to limit the data. For instance, under a User Country Filter you could select the United States so the data of the dashboard will only include that which came from users located in the United States. You can switch to ‘Exclude' by pressing the three dots to the right of the filter name when hovering. Be sure to take advantage of these filters to dig deeper into your games' data.
Unlike some values which will only display the aggregation of the indicated period, these values will adjust based on the length of time set in the Date filter. Use this filter to change the aggregated time period of the dashboard and these values will adjust as well.
In contrast to regular single values, daily average single values will not increase as the period increases. For example, ARPPU will rise as the period rises because of the same users making repeated payments. Average Revenue Per Paying Daily Average User (ARPPDAU) will not because it is the average of all the daily averages of the period, not the total payments and total paying users.
If you select a certain period, such as four weeks, with the Date filter, the data will show up segmented by weeks and display four. The aggregation for these weeks will be for all activity in that week, not the average of all the daily averages that are displayed when the graph is showing daily.
Parallel Period graphs will allow you to do trend analysis. If the x-axis is displaying days, then the 28D ago line will be the value recorded 28D ago. The same goes for 14D ago and 7D ago. The lighter the line, the farther back the period.
Moving averages are another way to conduct trend analysis. The time frame used in the calculations is displayed in the metric name. Understandably, longer timeframes will show a less volatility and show you the overall trend of the period. We use a simple moving average.
If you would like to download data directly from charts you may do so. Simply right click on the chart and you can download the data as CSV, XLS, and for use in presentations, PNG.
The Revenue dashboards offers several different ways to perform trend analysis. Included in this dashboard are parallel period, moving average, and growth charts which can all help you understand where the data is going. It also contains a currencies sheet so you can make sure you are offering all of the currencies for the areas in which you operate.
The Cancellations dashboard will allow you to keep tabs on fraud in your game. The overview sheet will show the number of cancellations by Cancellation Date, Payment Date, as a percent, and geographically. The reasons sheet gives you the ability to see the distribution of reasons for each cancellation.
All of these pre-defined dashboards are great, but what if you want to create your own? You can do this with the provided Xsolla Dataset! You can create an unlimited amount of dashboards with your Slemma account around your data; build any chart with any of the dimensions and measures.
Dimensions are how data is separated. These are not the values themselves, but a certain category of values. Every time you use a filter you are filtering by a dimension of the data. Examples of dimensions are Country, Credit Card Type, Date, etc.
|DateTime||Default date for all charts is in UTC timezone. This date is based on last payment status update(invoice, payment, cancellation). Example: when you want to add payments and cancellations count to one timeline payments will be aggregated by payment date and cancellations aggregated by cancellation date.|
|DateTime||Date of invoice in UTC timezone.|
|DateTime||Date of payment confirmation in UTC timezone. This date is available only for completed payments and not available for unpaid invoices.|
|DateTime||Date of payment cancellation in UTC timezone. This date available only for cancelled payments.|
|Projects||Project ID and Project Name|
|Payment System||Payment System Group e.g. Cash Payments, Bank Transfer|
|Payment System||Payment system ID and name, e.g. 24. Paypal, 57. PaySafeCard|
|Geography||User country detected by Xsolla system. This country is most accurate and complete. User IP, mobile operator country, credit card issiung bank country and other attributes are used for this lookup. This country is used internally in country selection for VAT calculation.|
|Geography||Language 2-letter code, e.g. EN, PT, RU|
|Geography||User location based on IP address lookup. This hierarchy contains accurate geo information from Region and Country to Country Subdivision and City.|
|Geography||User timezone detected based on user IP address, e.g. Europe/Berlin, America/Chicago|
|Geography||Business Region of User Country, e.g. European Union, Latin America|
|Geography||Payment system country of origin|
|Geography||Country of the bank that issued user's card|
|Currencies||Currency which is used in user payment in 3-letter code, e.g. USD, EUR|
|Currencies||Currency which is used in transfer to partner bank account in 3-letter code, e.g. USD, EUR|
|Purchase||Xsolla module used for this payment, e.g Virtual Items, Virtual Currency|
|Purchase||True if first payment for current user, false otherwise|
|Credit Cards||True if payment made by credit card, false otherwise|
|Credit Cards||Bank issued user credit card|
|Credit Cards||e.g VISA, MasterCard|
|Credit Cards||e.g. CREDIT, DEBIT|
|Credit Cards||e.g. CLASSIC, GOLD, PLATINUM|
|Credit Cards||True if user requested Xsolla save his/her payment system account credentials, false othewise|
|Credit Cards||True if payment was made from account credentials previously saved in Xsolla system, false otherwise|
|Credit Cards||True if credit card is rejected from payment processing, false othewise. Reject reason can be reviewed in Credit Card Reject Reason dimension|
|Credit Cards||e.g. Insufficient Funds, Did not pass validation 3D-secure|
|Recurring Payments||True if recurring subscription is created from payment, false otherwise|
|Recurring Payments||True if card was recharged because of recurring subscription, false otherwise|
|User Agent||User device operating system, e.g. Windows 8, MacOS, Android|
|User Agent||User browser, e.g. Firefox, Chrome Mobile|
|User Agent||Model of the user mobile device, e.g. IPhone, Nokia Lumia|
|User Agent||User device screen size resolution|
|User Agent||Xsolla User Interface used for payment, e.g. PayStation, Smartphone Version|
|Developers||Duration of payment processing time on Xsolla side e.g. 1-3 seconds, 1-10 minutes|
|Developers||Duration of payment processing time on payment system side, e.g. 1-3 seconds, 1-10 minutes|
|Developers||Total duration of payment processing e.g. 1-3 seconds, 1-10 minutes|
|Cancellations||True if payment is cancelled, false otherwise. Cancellation reason can be reviewed in Cancellation Type dimension|
|Cancellations||Reason for transaction cancellation, e.g. Refund, Chargeback|
Measures, in contrast to dimensions, are the values that are actually graphed on your charts. Examples of measures are Revenue, Paying Users, Conversion, Average Payments Amount.
|Measures||The amount of the successful user Payment. The sum before deduction of commissions. The amount is converted into the currency of the metric with exchange rate on the date of project notification.|
|Measures||Revenue divided by Payments count|
|Measures||Amount of income Revenue excluding Cancellations Revenue for the same period|
|Measures||Total count of completed payments. Payments may be cancelled in future periods|
|Measures||Amount of purchased virtual currency. Available in Virtual Currency integration module|
|Measures||Average Revenue Per Paying User: Revenue divided to unique Paying Users. When you use weekly or monthly aggregation, ARPPU grows significantly because one user can have multiple Payments in one time period|
|Measures||Total Payments count divided by unique Paying users count. Useful in weekly and monthly aggregation for payments frequency analysis|
|Conversion||Total count of created invoices|
|Conversion||Total users count who created an Invoice. Users who did not complete payments are included.|
|Measures||Count of unique users that made a Payment at least once in the considered period|
|Conversion||The percentage of the users who complete payment according to the total count of users who create invoice. Paying Users Percent is more accurate conversion metric (comparing with Paid Invoices Percent), since user can try a few payment options before they make an actual payment|
|Conversion||The percentage of the complete Payments according to the total count of Invoices|
|Conversion||Count of the users that created invoices but did not pay for it|
|Conversion||The percentage of the user created invoice but didn't pay for it|
|Conversion||Count of invoices which were not completed by the user and not confirmed by payment system|
|Conversion||The percentage of the Unpaid Invoices according to the total count of invoices|
|Conversion||Count of unique Paying users, who made their first payment in the current period|
|Conversion||The percentage of the New Paying Users according to the total count of Paying Users|
|Conversion||Count of unique Paying Users, who complete non-first payment|
|Cancellations||Count of Payments which were refunded or canceled|
|Cancellations||The percentage of the Cancellations to the total count of Payments.|
|Cancellations||Amount of the canceled Payments.|
|Cancellations||The percentage of the Cancellations Revenue to total Revenue.|
|Developers||Duration of payment processing time on Xsolla side|
|Developers||Duration of payment processing time on payment system side|
|Developers||Total duration of payment processing|
Measures can be aggregated in different ways. Here are descriptions of each type of aggregation you will see when viewing your dashboards:
|Count||How many of the tracked event occurred. Default for Invoices, Paying Users, etc.|
|Sum||What was the total sum of the numeric values associated with the event being tracked. Default for Gross Revenue, Virtual Currency Amount, etc.|
|Average||What was the average value of the measure. This will be used for measure such as percentages because it would not make sense to use Sum. Default for Average Payment Amount, Churn Users Percent, etc.|
|Maximum||What was the highest value that occurred for the measure.|
|Minimum||What was the lowest value that occurred for the measure.|
Q. How much is it?
A. It's free for all Xsolla customers.
Q. How can I activate data portal for my account?
A. You need to have an active project with completed payments. You can activate the data portal in Publisher Account
Q. What currency is the data in?
A. There are three currencies available: US dollar, Euro and Russian ruble. There is also an option to filter data in the payment currency.
Q. How can I upload my own data to Slemma?
A. You have several options to upload additional data: upload files from your computer or cloud storage, or connect directly to your database. You can learn more at the Slemma knowledge base
Q. I'm concerned about my data privacy and security.
A. We store all data in our secure Xsolla data warehouse inside Amazon Web Service's isolated private cloud. All data transferred in and out of the warehouse is through TLS encrypted connections. Raw payments data is not available in Slemma. Only aggregated data without personal user information is available. We applied principles of least privilege, firewalls, encryption, and other technical and operating approaches to keep your data safe.
A. Send us a feature request via email firstname.lastname@example.org
Q. Is it possible to download data from Slemma?
A. You can download charts and their data in different formats from Slemma by right clicking on the object and selecting the file type. You can also download entire dashboards as PDFs and PNGs. If you need raw data, you can use Xsolla Reports API
Q. Can I use this analytics for verifying or financial reports?
A. No, the data might be not 100% accurate since it's using average daily exchange rates.
Q. How often is the data updated?
A. The data gets updated daily at 2:00 AM UTC
Q. How precise are the metrics?
A. We fetch all metrics on-the-fly from raw data stored in our data warehouse. This approach guarantees accuracy for metrics with any combination of grouping and filtering, especially for distinct-count and average metrics, for instance Paying Users and Average Payment Amount. However, we don't provide totally accurate finance data because we convert payment amounts to different currencies with daily average exchange rates and apply two digit rounding to resulting values. That being said, the end difference is rarely greater than $0.01.
Q. How can I invite other users for collaboration?
A. When you activate the analytics in Publisher Account you can choose members of your team to invite (all members by default). When logged in to Slemma, you can invite new users in Users and groups settings.
Q. Can I create my own reports?
A. Yes you definitely can!
Q. What team features does Slemma provide?
A. Team sharing of dashboards, commenting, annotations, permission control, and dashboard automated deliveries.
Q. I have another question about Slemma…
A. Use the ‘Click here for help' widget on the left bottom side in Slemma to access their knowledge base or contact support with the same widget.
Q. How do I to link several xsolla publisher accounts together in Slemma?
A. Contact us at email@example.com
Q. I didn't find my question in this list…
A. Feel free to contact us with any questions at firstname.lastname@example.org