⚡️ Other integrations

Categorizing your subscribed customers

Auto-categorize your paying customers and track their recurring revenue, renewal date, and more

To enable auto-categorization of your subscribed customers, navigate to Lifecycle Tracking -> Subscribed Customers in your Account Settings (or get there via Quick Jump). There, you'll see a handful of options you'll need to configure in order to correctly categorize your subscribed customers.

Option 1 - select the traits that identify revenue

Select the trait(s) that specifies each customer's revenue - e.g. the mrr trait. If you select multiple traits here, we'll set the account's revenue to the first trait they have a value for.

Option 2 - define the condition that determines paid customers from trials (optional)

Sometimes, you may send revenue data even if the customer isn't paying you yet. For example, let's say this is your setup:

For trials

  • An account can view your available pricing plans and choose one to start a 30-day trial on

  • When an account starts their trial with their selected plan, you set a revenue trait to the price of their selected plan and a isTrial trait to true.

For trials converting to paid plans

  • The trial can view your available pricing plans and select one to start paying for.

  • When the account submits their payment for their selected plan, you update their isTrial trait to false

In this scenario, both your trials and your paying customers have the revenue trait set. But, trials aren't yet paying, so it's best to exclude them from revenue tracking until they actually convert to a paid plan (otherwise, your MRR will be inflated). To do that, you'd want to configure this step to only track customers where isTrial is set to false:

Options 3 - select the traits that identify the currency of the customer's revenue (optional)

If you have customers paying in multiple different currencies and want Vitally to automatically convert your revenue into a single currency (for accurate revenue reporting), follow these steps:

  • First, configure the currency you'd like to convert all revenue in to (and thus use in reports in Vitally) by following the instructions here. We call this your home currency.

  • Then, ensure you send Vitally an account trait that tracks the ISO 4217 currency code that the account's revenue is tracked in. For example, if you select a revenue trait in option #1 above and have some customers with a revenue value in Euros and others in USD, then be sure to track a trait with a value of EUR for those paying in Euros and a value of USD for those paying in USD. Note that the code can be sent in any case - e.g. USD, usd, uSD are all valid values.

  • Finally, select the trait that tracks the customer's currency in this option.

Vitally will then automatically convert your customers' revenue, regardless of currency used, into your selected 'home currency'. Vitally currently supports over 65 currencies with exchange rates updated daily.

Currently, Vitally automatically adds a currency account trait to your accounts whenever you connect any of our current supported revenue integrations - i.e. Stripe, Recurly, and Chargebee. Thus, all you need to do if you're using one of those integrations is select that currency trait here!

Options 4 & 5 - track the subscription period (optional)

If at all possible, we recommend tracking renewal dates alongside revenue. This way, you can use that data when filtering and creating Indicators (e.g. flag unengaged customers with a renewal in less than 7 days). So here, you'll want to identify the event properties or traits that track the start and end of a customer's subscription (if available).

Option 6 - Monthly vs yearly subscriptions

This step simply allows you to specify whether revenue is always sent as MRR, ARR, or as the value of the entire subscription period. If you select Total Subscription Period Cost here, we'll simply calculate a customer's MRR by dividing revenue values by 12 if the subscription period is longer than 1 month. If it is not, we won't modify the revenue value and will assume it is MRR.