Stripe is a global online payment platform that allows businesses to accept and process payments securely, effortlessly enabling e-commerce transactions. It provides tools for managing subscriptions, building marketplaces, and handling complex payment flows, making it a popular choice for businesses of all sizes.
Whether you’re building a marketplace, mobile app, online storefront or subscription service, Stripe has the features you need to accept payments online and within mobile apps.
With Databox, your most important Stripe KPIs will be transformed into meaningful insights and delivered to your mobile, Apple Watch, TV display or Slack channels. One of the key benefits of Databox is the ability to combine multiple data sources in one place.
SEMrush
Relative Visibility is a SEMrush metric that measures a website's visibility compared to its competitors in the same market, based on organic search results and the keywords they rank for.
SEMrush
The Keywords in TOP 10 metric shows the number of organic search keywords for which a domain or URL ranks in the top 10 search results on Google. This helps to assess the search engine visibility and ranking performance of a website.
SEMrush
The Average Position metric in SEMrush measures the typical rank of a website's organic search results for targeted keywords over a certain period.
SEMrush
Keywords in TOP 3 is a SEMrush metric that shows the number of keywords for which a domain or URL ranks in the top 3 search engine results pages. It indicates a site's visibility and potential traffic from high-ranking and relevant search queries.
SEMrush
Keywords in TOP 20 is a SEMrush metric that shows the number of keywords a website ranks for in the top 20 search engine results pages. It helps gauge a website's search visibility and SEO performance.
SEMrush
Keywords in Top 100 is a SEMrush metric that shows the number of keywords for which a domain or URL ranks in the top 100 search engine results pages (SERPs). It helps to evaluate the domain's or URL's visibility and track SEO performance.
SEMrush
SEMrush Site Audit Score is a comprehensive metric that evaluates the technical health of a website and assigns a score out of 100, indicating critical issues, warnings, and recommendations for improvement.
SEMrush
Estimated Traffic is a metric in SEMrush that shows the estimated monthly search traffic that a particular domain, subdomain, or URL receives from Google's organic search results.
SEMrush
This metric shows the top keywords that bring traffic to a website, excluding those that include the business name. It includes both local and hotel searches, and displays the position of each keyword in search results.
SEMrush
Domain Organic Keywords is a metric that shows the total number of organic keywords that a domain or website is ranking for in Google search results. It is an important indicator of a website's SEO performance and traffic potential.
SEMrush
Authority Score is SEMrush's domain-level metric that predicts a website's ability to rank in search engines based on backlink strength, quality, and quantity.
SEMrush
Domain Organic Traffic is a SEMrush metric that measures the amount of traffic a website receives from organic search, excluding paid search. It helps to analyze the website's overall SEO performance and identify opportunities for improvement.
SEMrush
Pages Crawled metric in SEMrush represents the number of pages on a website that were crawled by the SEMrush bot during a specific time period. This metric gives an indication of the size and structure of a website, and helps to identify any crawling issues.
SEMrush
The Errors metric in SEMrush shows the number of technical website issues detected during a site audit. These errors can negatively affect site performance and should be fixed to improve overall SEO health.
SEMrush
The Warnings metric in SEMrush indicates potential issues with a website's SEO performance, including technical errors, security issues, and other factors that could harm the site's rankings.
SEMrush
Backlinks refers to the number of links pointing to a website from other external sites. It is an important SEO metric that can impact search engine rankings and website authority. SEMrush offers various backlink metrics, including referring domains, backlink types, and the authority of referring domains.
SEMrush
Top Keywords by Position is a SEMrush metric that displays a list of keywords that a website ranks for in search results, where the website appears in the top positions. This includes local, hotel, and business name keywords. It helps to identify the website's most valuable keywords and top competitors.
SEMrush
The Notices metric in SEMrush is a count of the number of website issues detected by SEMrush Site Audit tool that require attention but are not as critical as errors or warnings.
SEMrush
Referring Domains is the number of unique domains that link to a website. It gives an idea of the website's backlink profile and its authority in search engine ranking.
SEMrush
Absolute Visibility is a SEMrush metric that gives you a percentage indicating how visible a domain or URL is in search results, taking into account all its ranking keywords.
Show more...
AdMob dashboard template which will give you insights about performance metrics to help you see where the right tweaks can increase profits.
Databox is using Stripe API for Data Source connection and for fetching the metrics data. Authentication is done by a Restricted API key with ‘Read Only’ access selected, as explained in the ‘How to connect Stripe to Databox‘ article. Databox is a Verified Technology Partner listed in the Stripe Partner Directory.
Some users may experience long loading times for Stripe metrics in Databox when:
This behaviour can occur in cases when there are large amounts of data present in the Stripe account. In such cases, long loading times are expected.
Databox needs some time to fetch and process all the data from the source due to the pagination and rate limit rules set by Stripe API. In some cases, depending on the amount of data in the Stripe account, it could take up to several hours for the metrics values to load.
If your subscriptions contain multiple subscription items and a discount is applied to a subscription, this will affect the related metrics in such a way that the total value of those metrics will be higher than the total value of equivalent non-dimensional standard metric, as subscription discounts cannot be divided among multiple subscription items.
Example for ‘MRR by Plan Name’:
Each subscription has subscription items applied (products/plans etc.). When a discount is applied, it is valid across all items/products. For example, there is a subscription with the following items:
All items above will be summed up (650$) and will count towards the total MRR (also for MRR by Plan Name metric).
Discounts can be applied only to the whole subscription, not one specific item. This means if there is s $200 discount applied to the subscription, we cannot subtract this amount from items, since there is no ‘ratio’ across subscription items. In this case, we will subtract $200 from the root MRR value ($650 – $200 = $450), while the dimensions SUM of ‘MRR by Plan Name’ will stay 650$.
This limitation applies to the following metrics:
MRR by Plan Name
New MRR by Plan Name
MRR (excl. Canceled Subscriptions) by Plan Name
Churned MRR by Plan Name
Churned MRR (Delinquent) by Plan Name
ARR by Plan Name
New ARR by Plan Name
Churned ARR by Plan Name
ARR (excl. Canceled Subscriptions) by Plan Name
If there are several purchases in different currencies in Stripe, Stripe converts and sums together those values in Stripe using estimated conversion rates – as a result data is displayed in one currency in the Stripe User Interface.
However, the Stripe API is returning raw data in the original currencies and does not include estimated currency conversions. Hence, the users who have multiple-currencies purchases enabled in their Stripe account will notice the discrepancy when comparing the Revenue-related metrics to Databox.
While the exact number as in the Stripe User Interface will not be possible to display in Databox, the workaround solution is to use calculated metrics in Databox to convert the values into one currency and sum them together.
When you first use a Stripe metric in Databox, 12 months of historical data is initially synced for all metrics with the exception of charge-related metrics and metrics of current or calculated type.
When Charge metrics are first used in Databox, 24 months of historical data is available for them. Charge metrics are:
Payments,
Gross Volume,
Successful Charges,
Failed Charges.
Metrics of Current and Calculated metric types, such as Customers and Available Balance, will have data available in Databox from the day when they are first used in the Databox app, but not for dates prior to that. The metric type information is available under the ‘Tech details’ tab of the metric description in the Metric library.
For all Stripe metrics, due to the pagination limitation of Stripe integration, the maximum number of fetched charges, subscriptions, refunds, customers, transactions, invoices, etc. is 100,000 (100k) for the selected Date Range.
Data discrepancies between Databox and Stripe’s User Interface may occur for Stripe metrics. This is due to a difference in how Databox calculates data synced from Stripe’s API vs. how data is calculated in the Stripe User Interface.
The description of each Stripe metric and how they are calculated is specified in this article.
For all ‘by Plan Name’ dimensional Stripe metrics, Databox shows the plan nickname (as received from the API response) in place of the Plan Name.
If the nickname is missing in the Stripe account for the specific plan or all plans, Databox will instead show the Plan ID, as mentioned in the help article.
Hence, it is recommended to set the nicknames for plans in the Stripe account.
This error may occur if there is a large amount of data in the Stripe source and it needs to be synced into Databox. The error will appear on the Metric Insights or Forecasts page.
Databox needs some time to fetch and process all the data from the source following pagination and rate limit rules set by Stripe API. When that time exceeds the timeouts for the Metric Insights and Forecasts query, the ‘We are experiencing some temporary issues. Please try again in a minute.’ error message will be displayed.
The workaround is to check the same metric insight or forecast later – up to a few hours, as Databox will continue the fetch the data in the background after the error message appears. Additional fetch duration optimization can be done in cases where the specific Stripe metric is already in use in the Databox account, as the past historic data will be stored in the Databox warehouse.
Usage
Upgrades or downgrades are tracked when they actually happen. For example, if a user moved from PlanA ($59) to PlanB ($119) today, an upgrade of $60 will be tracked. The same logic will apply to downgrades.
In cases where the user would switch back and forth, every upgrade and downgrade would be tracked and would influence the upgrade or downgrade amount in Databox. Therefore, Databox suggests using the Calculated Metrics to track the Net New Upgrade or Downgrade values.
Below is an example of the MRR Upgrades metric and the same logic will apply for other Upgrades and Downgrades metrics.
Net New MRR Upgrades = MRR Upgrades – MRR Downgrades
Limitation
To calculate upgrades, downgrades, and reactivations we use the /events endpoint. In accordance with the Stripe API documentation, Databox can collect only 30 days of historical data through this API endpoint.
For example, if an upgrade occurred 31 days ago, it would not be pushed to and visible in Databox today.
