Data Overview

Chargify exposes five core entities through Coupler.io. Each one maps to a key part of your subscription billing operation — from who your customers are to how money moves through your system.

Entities summary

Entity	Primary use
Customers	Customer directory and contact data
Subscriptions	Recurring revenue tracking and lifecycle analysis
Invoices	Billing records and payment status
Coupons	Discount campaign performance
Transactions	Payment history and financial reconciliation

Customers

Key fields

Field	Description
id	Unique Chargify customer ID
first_name / last_name	Customer name
email	Primary contact email
organization	Company name (if B2B)
created_at	Date the customer record was created
updated_at	Date the record was last modified
reference	Your internal ID for this customer

Subscriptions

Key fields

Field	Description
id	Unique subscription ID
state	Current status (active, canceled, trialing, past_due, etc.)
product_name	Name of the subscribed product/plan
current_period_ends_at	End of the current billing cycle
trial_ended_at	When the trial period ended
activated_at	When the subscription became active
canceled_at	Cancellation date (if applicable)
total_revenue_in_cents	Lifetime revenue from this subscription
product_price_in_cents	Current plan price
customer_id	Link back to the customer record

Invoices

Key fields

Field	Description
uid	Unique invoice identifier
number	Human-readable invoice number
status	Payment status (paid, pending, voided)
total_amount	Total invoice amount
due_amount	Remaining amount due
paid_date	Date the invoice was paid
issue_date	Date the invoice was issued
subscription_id	Associated subscription

Coupons

Key fields

Field	Description
id	Unique coupon ID
code	The discount code string
discount_type	Percentage or flat amount
percentage / amount_in_cents	Discount value
redemption_limit	Max number of uses
times_used	How many times the coupon has been redeemed
end_date	Expiry date
created_at	When the coupon was created

Transactions

Key fields

Field	Description
id	Unique transaction ID
transaction_type	Type (payment, refund, credit, etc.)
amount_in_cents	Transaction amount
success	Whether the transaction succeeded
created_at	Transaction timestamp
subscription_id	Linked subscription
customer_id	Linked customer
gateway_used	Payment gateway that processed the transaction

Common metric combinations

• MRR by plan — Subscriptions filtered by state = active, grouped by product_name, summing product_price_in_cents

• Churn rate — Subscriptions with state = canceled, count over time using canceled_at

• Revenue collected — Transactions filtered by success = true and transaction_type = payment, summing amount_in_cents

• Coupon effectiveness — Coupons joined to Subscriptions to see conversion rate per discount code

• Overdue invoices — Invoices filtered by status = pending with due_amount > 0

Use cases by role

Finance teams

• Pull Invoices and Transactions into Google Sheets or Excel for monthly revenue reconciliation

• Use the Aggregate transformation to sum amount_in_cents by month for cash flow reporting

• Join Transactions with Subscriptions to reconcile payments against active plans

• Send overdue invoice data to ChatGPT or Claude for draft follow-up email suggestions

Revenue/Growth teams

Customer success

Platform-specific notes

• All monetary values in Chargify are stored in cents — divide by 100 for dollar amounts in your reports

• The state field on Subscriptions is the most important field for segmenting active vs. churned revenue

• Chargify uses a site-based data model — if you run multiple Chargify sites, each requires its own connection with a separate subdomain and API key

• Coupons are scoped to a product family in Chargify; the exported data reflects this structure

• Deleted customers may still appear in transaction history for audit purposes