How do providers contribute over time?
- dataset
- Revenue transactions
- rows
- Provider
- columns
- Month
- measures
- Net proceeds
Filter to USD and the production environment. Provider rows have different grains, so do not compare their row counts.
Imported transaction field crosswalk
This describes AppRoute’s normalized Revenue transactions dataset, not every field available in either provider. Exact coverage depends on the connected account, provider permissions, and the source record.
| Pivot field | Stripe import | RevenueCat import | How to use it |
|---|---|---|---|
| Provider | Stripe | RevenueCat | Separate web-payment and mobile-purchase sources. |
| Store | Shown as web when no store is attached | App Store or Google Play when recognized in Charts v3 | Use for store comparisons only where the provider supplied a recognized value. |
| Product | Resolved Stripe product when available | Not populated in production Charts v3 rows | Use product reporting for Stripe. RevenueCat production proceeds appear in an unassigned product group. |
| Customer | Stripe customer identifier when available | Not populated in production Charts v3 rows | Customer counts and revenue-per-customer are not available for the production RevenueCat proceeds import. |
| Transaction kind | Payment or retained account adjustment | Production Charts v3 rows are normalized as adjustments | Do not interpret a RevenueCat row as an individual purchase, renewal, or refund. |
| Status | Succeeded, pending, failed, or refund state | Production proceeds rows are recorded as succeeded | Use Stripe status filters for payment-state questions; RevenueCat Charts does not supply the same transaction detail. |
| Currency | Charge currency | USD in the current production Charts v3 import | Filter to one currency before adding money values. |
| Date / month | Provider event time in UTC | Daily Charts v3 proceeds date in UTC | Compare time periods while respecting each dataset’s different grain. |
Measures and their limits
The pivot exposes the normalized measures that can be derived from imported rows. A blank or unavailable value should not be read as zero.
| Measure | Meaning | Coverage note |
|---|---|---|
| Gross revenue | Sum of positive recorded amounts | Use for Stripe rows. Production RevenueCat Charts rows do not populate gross amount. |
| Refunds | Recorded refund magnitude | Use for Stripe rows. Production RevenueCat Charts rows do not expose individual refunds in this import. |
| Known fees | Fees exposed by the provider record | Use for Stripe rows where fees are known. Production RevenueCat Charts rows do not populate fees. |
| Net proceeds | Provider proceeds after available fees, refunds, and adjustments | The supported money measure for current production RevenueCat Charts rows; still reconcile the selected period with RevenueCat. |
| Transactions | Count of normalized dataset rows | For RevenueCat production data this counts daily store-proceeds rows, not purchases. Do not compare it with Stripe payment counts. |
| Customers | Distinct customers within a grouped cell | Available only where customer identifiers exist; current production RevenueCat proceeds rows have none. |
| Revenue per customer | Net proceeds divided by distinct customers | Not available for current production RevenueCat proceeds rows; Stripe subtotals can still be approximate. |
Three AppRoute pivot recipes
Connect a provider in Dashboard → Integrations, let the import finish, then open Statistics → Pivot table. Revenue imports and revenue pivots require Pro or Team and use personal-account revenue rather than a combined team-workspace total.
Which Stripe products account for refunds?
- dataset
- Revenue transactions
- rows
- Product
- columns
- Month
- measures
- Refunds + Gross revenue
Filter Provider to Stripe and keep the unassigned product group visible.
How do RevenueCat stores compare?
- dataset
- Revenue transactions
- rows
- Store
- columns
- Month
- measures
- Net proceeds
Filter Provider to RevenueCat. Current production data is daily USD proceeds by store; reconcile the selected period with RevenueCat.
Reconcile before sharing the report
Use the same date range, timezone, environment, currency, refund treatment, and provider metric definition. Record filters with the exported table so another person can reproduce it.
1. Name the question
State whether you need gross sales, proceeds, refunds, transactions, or customer behavior.
2. Choose one dataset
Use Revenue transactions for normalized money movements or Revenue metrics for RevenueCat daily account metrics.
3. Lock the reporting scope
Select the date range, production environment, provider, and one currency before comparing totals.
4. Inspect missing groups
Keep unknown product, customer, store, and fee values visible until you understand why they are absent.
5. Compare with the provider
Run the closest Stripe or RevenueCat report using the same boundaries and document any expected difference.
6. Export the visible pivot
Save the CSV together with its rows, columns, measures, filters, date range, and reconciliation note.
Keep exploring