Recurly

Recurly is a subscription billing and revenue management platform designed to simplify and automate recurring billing processes for subscription-based businesses. It provides a suite of tools and features to help businesses manage their subscription plans, billing cycles, and customer payments effectively.

Data Schema

Setup Guide

Step 1 - Get API Key

1. Log in to Recurly.
2. In the navigation bar on the left, select Integrations > API Credentials.
3. Find your private API key and make a note of it. You will need it to configure Weld.

Step 2 - Begin Configuration

1. In the connector setup form, enter the destination schema name of your choice.
2. Enter the API Key that you copied from step 1.
3. Select the location where your recurly is hosted.

Step 3 - Data To Sync

1. Select the pre-built reports you wish to include in the sync.
   You can view the schema, remove columns or hash sensitive information.

Step 4 - Configure Sync

1. Select how often you would like the data to sync.
2. Check the Destination schema name, which is where the tables land in your warehouse, and click Start Initial Sync.

Weld will take over from here and commence syncing data from your Recurly account.

SQL Templates

View all →

Billing by month

What was invoiced, credited, collected and still owed, by month. The cash-side companion to the MRR models, and the closest match to Recurly's invoice export totalled by month.

grain: month x currency · builds on 1 model

MRR by customer month

MRR per customer per month, and the movement that took it there: new, expansion, contraction, churn or reactivation.

grain: month x customer (Recurly account) x currency · builds on 4 models

MRR movements

The MRR bridge by month: opening MRR, new, expansion, contraction, churn, reactivation, closing MRR, plus customer counts. The movements Recurly's subscription analytics show, rebuilt from invoiced line items.

grain: month x currency · builds on 5 models

Subscription churn

Every subscription that has ended, why it ended, and how much MRR it was carrying just before. Splits churn into customers who chose to leave and customers lost to failed payments, which the MRR bridge cannot tell apart.

grain: one row per expired subscription · builds on 5 models