Exporting Data
You can export Subscription, Customer, and Transaction data to a CSV file. Simply visit each tab in the UI and look for the “Export” link. After creating an export, the user who initiated it will receive a notification in-app and via email when the export is ready for download. You can also use our API to extract data.
Your notification settings can be updated at: https://app.chargify.com/notification/settings/edit
Export Time Length
In every scenario, Chargify attempts to generate reports as quickly as possible. There are lots of factors that affect how quickly exports are generated within Chargify. Specifically, the number of merchants exporting reports can affect report generation.
In the event that a report is running slower than anticipated, we encourage you to be patient. In the event that an export fails or does not complete within 30 minutes, please contact our support team here.
Locating Exports
If you are exporting multiple items, or would like to refer to previously exported data, Chargify stores a list of your recent exports.
Simply click the gear in the upper right hand corner of the dashboard and select ‘Downloads’ from the list.
When you select the Downloads option, you’ll see a list of your recent exports. Additionally, you can elect to re-download your exports or remove them from the list.
Customers Export
Title | Description | Column |
---|---|---|
id |
The unique identifier for this customer within Chargify. This is the ID displayed in the customer tab | A |
first_name |
The first name of the customer | B |
last_name |
The last name of the customer | C |
organization |
Company/Organization name | D |
email |
The email address of the customer | E |
created_at |
The creation date for this customer. E.g: 2016-06-03 12:43:50 -0400
|
F |
reference |
The unique identifier used within your own application for this customer | G |
address |
The customer’s shipping street address (i.e. “123 Main St.”). | H |
address_2 |
Second line of the customer’s shipping address i.e. “Apt. 100” | I |
city |
The customer’s shipping address city (i.e. “Boston”). | J |
state |
The customer’s shipping address state (i.e. “MA”) | K |
zip |
The customer’s shipping address zip code (i.e. “12345”) | L |
country |
The customer shipping address country, perferably in ISO 3166-1 alpha-2 format (i.e. “US”). | M |
phone |
The phone number of the customer | N |
created_at |
TBD | O |
updated_at |
The date of last update for this customer | P |
cc_emails |
Additional email addresses that will communications | Q |
Invoices CSV
The invoices CSV export consists of the line items for each invoice, with the following columns:
Title | Description | Column |
---|---|---|
transaction_id |
The ID of the transaction (see API: Transactions ) | A |
created_at |
The creation date for this line item | B |
invoice_id |
The ID of the Invoice this line item belongs to (see API: Invoices ) | C |
invoice_number |
The unique (to this site) identifier for the invoice | D |
type |
See API: Transactions for a list of available transaction types | E |
memo |
A note about the transaction | F |
amount_in_cents |
The amount in cents of the transaction | G |
starting_balance_in_cents |
The initial balance on the Subscription before the Transaction has been processed | H |
ending_balance_in_cents |
The remaining balance on the Subscription after the Transaction has been processed | I |
subscription_id |
The subscription’s unique ID within Chargify | J |
customer_id |
The customer’s unique ID within Chargify | K |
customer_name |
The customer’s name | L |
product_id |
The product’s unique ID within Chargify | M |
product_name |
The product’s name | N |
kind |
The specific “subtype” for the transaction type (see API: invoices for a list of available subtypes) | O |
invoice_status |
The current status of the invoice | P |
invoice_settled_at |
The date the Invoice was settled at, if applicable customer_organization
|
Q |
coupon_name |
The coupon code, if the transaction kind is coupon | R |
Products Export
Title | Description | Column |
---|---|---|
id |
The product name | A |
name |
The product name | B |
handle |
The product API handle | C |
description |
The product description | D |
accounting_code |
The product family accounting code (has no bearing in Chargify, may be used within your app) | E |
product_family_id |
ID of product family within Chargify | F |
product_family_name |
Nested attributes pertaining to the product family to which this product belongs | G |
product_family_description |
Description of product family | H |
expiration_interval |
A numerical interval for the length a subscription to this product will run before it expires. See the description of interval for a description of how this value is coupled with an interval unit to calculate the full interval |
I |
expiration_interval_unit |
A string representing the trial interval unit for this product, either month or day
|
J |
return_url |
The url to which a customer will be returned after a successful signup | K |
update_return_url |
The url to which a customer will be returned after a successful account update. | L |
created_at |
Timestamp of the creation of the product | M |
price_in_cents |
The product price, in integer cents | N |
interval |
The numerical interval. i.e. an interval of ‘30’ coupled with an interval_unit of ‘day’ would mean this product would renew every 30 days |
O |
interval_unit |
A string representing the interval unit for this product, either month or day
|
P |
initial_charge_in_cents |
The up front charge you have specified. | Q |
trial_price_in_cents |
The price of the trial period for a subscription to this product, in integer cents. | R |
trial_interval |
A numerical interval for the length of the trial period of a subscription to this product. See the description of interval for a description of how this value is coupled with an interval unit to calculate the full interval |
S |
trial_interval_unit |
A string representing the trial interval unit for this product, either month or day
|
T |
archived_at |
Timestamp indicating when this product was archived | U |
require_credit_card? |
true/false: has a credit card been requested? | V |
request_credit_card? |
true/false: has a credit card been requested? | W |
return_params |
Additional return parameters that will be added to the end of the return URL | X |
request_shipping_address? |
true/false: has the shipping address been requested? | Y |
require_shipping_address? |
true/false: is the shipping address been required? | Z |
request_billing_address? |
true/false: has the billing address been requested? | AA |
require_billing_address? |
true/false: is the billing address been required? | AB |
update_return_params |
The parameters we will append to your update_return_url | AC |
Subscriptions Export
Title | Description | Column |
---|---|---|
id |
The subscription ID | A |
customer_id |
The ID of an existing customer within Chargify | B |
customer_reference |
The reference value (provided by you) of an existing customer within Chargify | C |
customer_name |
The full name of your Subscriber | D |
customer_email |
The email address of your Subscriber | E |
state |
The current state of the subscription. Please see the documentation for Subscription States | F |
product_id |
The Product ID of the product for which the Subscription exists | G |
next_product_id |
If a delayed product change is scheduled, the ID of the product that the subscription will be changed to at the next renewal | H |
product_name |
The given name of the product | I |
recurring_price |
The recurring price of the product | J |
recurring_interval |
The recurring interval of the product. Expressed in number of months or days | K |
recurring_interval_unit |
The unit of recurring period. Will be day or month
|
L |
coupon |
The numeric id of the coupon currently applied to the subscription | M |
created_at |
The timestamp of the creation of the subscription | N |
created_at_day |
The day of the month in which the subscription was created | O |
created_at_month |
The month in which the subscription was created | P |
created_at_year |
The year in which the subscription was created | Q |
current_period_starts_at |
Timestamp relating to the start of the current (recurring) period | R |
current_period_ends_at |
Timestamp relating to the end of the current (recurring) period (i.e.,when the next regularly scheduled attempted charge will occur) | S |
next_assessment_at |
Timestamp that indicates when capture of payment will be tried or retried | T |
trial_started_at |
Timestamp for when the trial period (if any) began | U |
trial_ended_at |
Timestamp for when the trial period (if any) ended | V |
activated_at |
The timestamp in which the subscription was activated | W |
expires_at |
Timestamp giving the expiration date of this subscription (if any) | X |
canceled_at |
The timestamp in which the subscription was canceled | Y |
canceled_at_day |
The day of the month in which the subscription was canceled | Z |
canceled_at_month |
The month in which the subscription was canceled. | AA |
canceled_at_year |
The year of cancelation | AB |
cancellation_message |
The cancelation reason/message | AC |
balance_in_cents |
The current balance in cents | AD |
balance |
The current balance | AE |
revenue_in_cents |
The revenue in cents | AF |
revenue |
The revenue | AG |
credit_card_masked_number |
The masked credit card on file. E.g. XXXX-XXXX-XXXX-1111 | AH |
credit_card_type |
The type of credit card | AI |
credit_card_first_name |
The first name listed on the credit card | AJ |
credit_card_last_name |
The last name listed on the credit card | AK |
credit_card_expiration_month |
The expiration month of the credit card on file | AL |
credit_card_expiration_year |
The expiration year of the credit card on file | AM |
credit_card_vault |
The location of the credit card token | AN |
credit_card_vault_token |
The credit card token | AO |
credit_card_customer_vault_token |
The credit card token. Used only by Authorize.Net | AP |
credit_card_billing_address |
The credit card or bank account billing street address (i.e. “123 Main St.”). | AQ |
credit_card_billing_address_2 |
Second line of the customer’s billing address i.e. “Apt. 100” | AR |
credit_card_billing_city |
The credit card or bank account city billing address | AS |
credit_card_billing_state |
The credit card or bank account state billing address | AT |
credit_card_billing_zip |
The credit card or bank account zip code | AU |
credit_card_billing_country |
The credit card or bank account billing address country, in ISO 3166-1 alpha-2 format (i.e. “US”). | AV |
shipping_address |
The shipping address | AW |
shipping_address_2 |
Second line of the customer’s shipping address i.e. “Apt. 100” | AX |
shipping_city |
The shipping city portion of the address | AY |
shipping_state |
The shipping state portion of the address | AZ |
shipping_zip |
The shipping zip portion of the address | BA |
shipping_country |
The shipping country portion of the address | BB |
customer_organization |
The customer’s organization | BC |
customer_phone |
The customer’s phone number | BD |
cancel_at_end_of_period |
True/false: if the subscription is set to cancel at the end of the current billing period | BE |
delayed_cancel_at |
Timestamp for when the subscription is currently set to cancel. expires_at Timestamp giving the expiration date of this subscription (if any) | BF |
product_version_number |
The version of the product the subscriber has purchased. Example: 80. 29, 31 | BG |
updated_at |
The timestamp of the most recent update to the subscription | BH |
referral_code |
BI | |
state_changed_at |
The timestamp of the most recent subscription state change | BJ |
cancellation_method |
The process used to cancel the subscription, if the subscription has been canceled. Can be one of merchant_ui , merchant_api , dunning , unknown , or billing_portal . |
BK |
reason_code |
The specific dunning reason code provided during cancellation of the subscription. | BL |
custom_fields |
A specific column that indicates the title of the custom field will be added if this is enabled in the custom field CSV settings. Each custom field will be a separate column. | |
Estimated Renewal Amount |
(Optional) This is the anticipated next billing amount, based on the current plan and configuration (taxes, components, discounts, etc.) You can enable this option under Settings –> CSV exports | varies |
Component name & ID |
(Optional) A separate column will be added for each individual component in your Site. Each column will be populated with the total number of currently allotted component. You can enable this option under Settings –> CSV exports | varies |
Tax History - Avalara
Use the following table to refer to the values provided from an export of tax histoy if you have Avalara enabled.
Title | Description | Column |
---|---|---|
id |
The unique identifier for the taxation charge | A |
taxation_id |
ID of the tax | B |
transaction_id |
ID of the transaction | C |
statement_id |
ID of the statement in Chargify | D |
subscription_id |
ID of the subscription in Chargify | E |
site_id |
ID of the site in Chargify | F |
rate_when_recorded |
Rate of tax when the tax was applied | G |
taxable_amount_in_cents |
Taxable amount in cents | H |
tax_amount_in_cents |
Amount of tax in cents charged based off the taxable amount | I |
description |
Description of the tax applied | J |
jurisdiction_name |
Name of jurisdiction applying tax | K |
jurisdiction_type |
Type of jurisdiction applying tax | L |
subdivision_code |
Subdivision under jurisdiction_type that has applied the tax |
M |
country_code |
Country code of applied tax | N |
recorded_at |
Timestamp of the date the tax was recorded in Chargify | O |
created_at |
Timestamp of the date the tax transaction was created in Chargify | P |
updated_at |
Timestamp of the date the subscription was updated at in Chargify | Q |
collected_at |
Timestamp of the date the tax was collected in Chargify | R |
Tax History - Custom Taxes
Use the following table to refer to the values provided from an export of tax histoy if you have custom taxes enabled.
Title | Description | Column |
---|---|---|
id |
The unique identifier for the taxation charge | A |
created_at |
ID of the tax | B |
type |
ID of the transaction | C |
memo |
Memo regarding the transaction | D |
amount_in_cents |
Amount in cents of the charge | E |
ending_balance_in_cents |
Ending balance of the current collected revenue | F |
subscription_id |
Subscription ID in Chargify | G |
customer_id |
Customer ID in Chargify | H |
customer_name |
Customer first and last name | I |
product_id |
Product ID that the taxation was applied to | J |
success |
Was the payment for the charge successful? | K |
kind |
Type of transaction | L |
payment_id |
ID of the payment | M |
gateway_transaction_id |
Transaction ID generated by the gateway | N |
customer_organization |
Customer organization | O |
gateway_order_id |
Gateway order ID (if applicable) | P |
Transactions Line Item Export
Title | Description | Column |
---|---|---|
id |
The unique identifier for the Transaction | A |
created_at |
Timestamp indicating when the Transaction was created | B |
type |
The type of the transaction: adjustment , tax , payment , refund , credit , charge , info_transaction
|
C |
memo |
A note about the Transaction | D |
amount_in_cents |
The amount in cents of the Transaction | E |
ending_balance_in_cents |
The remaining balance on the subscription after the Transaction has been processed | F |
subscription_id |
The unique identifier for the associated Subscription | G |
customer_id |
The ID of the customer | H |
customer_name |
The name of the customer | I |
product_id |
The id of the product purchased | J |
success |
true/false: was the transaction successful. In the case of a tax-based charge, success translates to “was tax charged”. If you would like to know if tax was collected, please view the custom or Avalara tax report. |
K |
kind |
The specific “subtype” for the transaction_type. May be one of the following: baseline , metered_component , on_off_component , quantity_based_component , coupon , trial , one_time
|
L |
payment_id |
The unique identifier for the payment being explicitly refunded (in,whole or in part) by this transaction. Will be null for all transaction,types except for “Refund”. May be null even for Refunds. For partial,refunds, more than one Refund transaction may reference the same,payment_id. | M |
gateway_transaction_id |
A gateway-specific identifier for the transaction, separate from the gateway_transaction_id | N |
customer_organization |
Organization of the customer | O |
gateway_order_id |
A gateway-specific identifier for the transaction, separate from the gateway_transaction_id.
|
P |
Finance Reports
Title | Description | Column |
---|---|---|
subscription_id |
The ID of the subscription. | A |
customer_id |
The ID of the customer. | B |
customer_first_name |
The first name of the customer. | C |
customer_last_name |
The last name of the customer. | D |
customer_organization |
The organization of the customer. | E |
customer_reference |
The reference for the customer. | F |
sale_number |
Sale/Invoice number. An internal Chargify field (i.e. not presented,elsewhere in our UI or API) that increases monotonically for each sale,event in your Site. | G |
sale_date |
The time which you made the sale specified by the SaleNumber. This is,generally the date that payment became due, and is the timestamp used,for the accrual-basis accounting in this report. | H |
sale_reason |
The reason the sale was recorded. One of: signup , renewal ,migration , reactivation , one_time_charge , imported_invoice , imported_statement , or refund
|
I |
category |
The category for the line, as it relates to the Finance Report. One of: Sales , Discounts , Credits/Voids , Taxes , Payments , or Refunds
|
J |
subcategory |
The subcategory for the line. | K |
sale_amount |
The sale amount of the line. Only applicable to lines in the “Sales” category. | L |
discount_amount |
The discount amount for the line. For lines in the Sales category, this,gives the discount on that particular line’s sale_amount. For lines in,the Discounts category, this gives the total discount amount attributed,to the Coupon identified by Item. | M |
tax_amount |
The tax amount for the line. For lines in the Sales category, this gives the tax computed on that particular line’s sale_amount . For lines in the taxes category, this gives the total tax amount attributed to the tax identified by Item. |
N |
credit_amount |
The amount of credit or void applied to the line. For lines in the sales, category, this gives the credit applied to that particular line. For lines in the credits/voids category, gives the amount of the credit/void. | O |
billed_amount |
The total amount billed to the customer, which includes taxes is reduced by credits. Only valid for lines in the Sales category. | P |
revenue_amount |
The total amount of revenue attributed to the line, which is the billed,amount with taxes removed. Only valid for lines in the Sales category. | Q |
payment_amount |
For Sales lines, this is the amount paid on the line (against the billed_amount). For payments lines, this is the total amount of the payment applied (potentially across many lines). | R |
period |
The recurring period for the subscription. Only valid for Sale lines with occasion other than one_time_charge or refund . |
S |
product_id |
The ID of the main product for the subscription. | T |
item_id |
A string that represents the Item associated with the line. e.g. “Product-123”, “MeteredComponent-456”, “Coupon-987”, etc. | U |
item_name |
The name of the Item | V |
transaction_id |
The Chargify transaction ID that corresponds with the line. | W |
transaction_memo |
The memo from the original transaction. | X |
document_uri |
The Chargify document that contains the original transaction. | Y |
MRR
Title | Description | Column |
---|---|---|
timestamp |
Timestamp indicating when the MRR event occurred | A |
category |
The type of the MRR event: new_business , expansion , reactivation , contraction , churn
|
B |
mrr_movement |
The growth (either positive or negative) using the site’s currency | C |
subscription_mrr |
The current MRR for the Subscription | D |
subscription_id |
The unique identifier for the Subscription | E |
subscriber_name |
The name of the subscriber | F |
description |
An English explanation of the MRR event. For example, “Delores Quigley increased Widgets to 64 (+47).” | G |
subscription_url |
Direct URL to the Subscription | H |
MRR Summaries
Title | Description | Column |
---|---|---|
time_period |
The time period indicating the reporting month and year | A |
new_business_amount |
The growth amount per the increase in the new business metric | B |
new_business_count |
The number of the events that occurred for new business | C |
expansion_amount |
The growth amount per the increase in expansion | D |
expansion_count |
The number of events that occurred for expansion | E |
contraction_amount |
The figure depicting the amount of decrease in MRR due to contraction | F |
contraction_count |
The number of the events that occurred for contraction | G |
churn_amount |
The figure depicting the amount of decrease in MRR due to churn | H |
churn_count |
The number of the events that occurred for churn | I |
reactivation_amount |
The growth amount in MRR due to reactivation events | J |
reactivation_count |
The number of the events that occurred for reactivation | K |
incremental_usage |
Growth in usage billings: how much more/less has been billed in the present month as compared to the last given month. If today is the 5th of the current month, we’ll compare the usage from 1st - 5th of the present month, as compared to the 1st - 5th of the previous month. | L |
net_movement |
Total net movement including incremental usage | M |
mrr |
Total traditional MRR for the given time period | N |
total_usage |
Total revenue of metered usage for the given period | O |
mrr_plus_usage |
The total MRR plus incremental usage for the given time period | P |
growth_rate |
The growth rate of the MRR for the given reporting period | Q |