Freemius data models in Chartsy
Exactly what Chartsy reads from one Freemius product, what each object becomes in Chartsy, and the access it needs.
How the sync works#
- First import - right after you connect, Chartsy reads your plans and pricing, coupons, users, subscriptions and payments, from 1 January two years back.
- Live updates - a webhook listener Chartsy adds to your product sends each new payment, refund and cancellation as it happens, signed with your product's secret key.
- Hourly catch-up - Chartsy reads Freemius's event log since the last run, so a missed webhook delivery is still picked up.
Every record is keyed on Freemius's own ids, so an event that arrives twice updates the same record instead of counting twice.
What Chartsy syncs#
| Freemius object | Becomes in Chartsy | What is kept |
|---|---|---|
| Plan | Product | Title, description, whether it is hidden, created date |
| Pricing tier | Up to three prices - monthly, annual and lifetime | Amount, currency and site count, named like Pro · 5 sites · Annual |
| Coupon | Discount | Code, percentage or fixed amount, whether it renews, start and end dates |
| User | Customer | Freemius user id, email, name, signup date, and country from their payments |
| Subscription | Subscription | Status (active, trialing, past due, canceled), amount per cycle including coupons, billing cycle, next payment, cancellation and trial dates, license and plan ids, gateway |
| Payment | Transaction | Gross amount, VAT, gateway fee, net amount, currency, country, whether it was a renewal, and the subscription it pays for |
| Refund or chargeback | Adjustment | Negative amount, tied to the payment it reverses |
Monthly and annual subscriptions count toward MRR; lifetime licenses count as revenue only. For how each metric is calculated, see the Freemius connection guide and Metrics.
What is left out#
- Sandbox data - test payments and subscriptions are skipped.
- Installs, license activations and emails - these Freemius events don't affect revenue, so they are acknowledged and dropped.
- License keys - Chartsy reads a license only for its expiry date, to time churn; it never stores the key.
- Payment details - Freemius doesn't share card numbers or bank details, and Chartsy never asks for them.
Access used#
Chartsy connects with your product's API Bearer Authorization Token and Secret Key from Settings → API & Keys. Both are encrypted at rest.
- The token reads your product's billing data. The only thing Chartsy writes with it is the webhook listener.
- The secret key is used only to check that webhooks really come from Freemius.
Already connected this product?
Each Freemius product can be connected once, even with a new token, so its numbers are never doubled.
Deleting your data#
Delete the Freemius source on the Data Sources page and it is permanently removed, together with everything imported from it. You can also remove the webhook listener in Freemius under your product → Webhooks → Listeners.
