Recurly
to
BigQuery

Connect Recurly to BigQuery with No Code

With Portable, you can sync Recurly data into your BigQuery warehouse in minutes. Access all of your Subscription Management data from BigQuery without having to manage cumbersome ETL scripts.

The Two Paths To Connect Recurly To Your Data Warehouse

There are two ways to sync data from Recurly into your data warehouse for analytics.

Method 1: Manually Developing A Custom Data Pipeline Yourself

Write code from scratch or use an open-source framework to build an integration between Recurly and your warehouse.

Method 2: Automating The ETL Process With A No-Code Solution

Leverage a prebuilt connector from a cloud-hosted solution like Portable.

Two Paths To Connect Recurly To Your Data Warehouse
Two Paths To Connect Recurly To Your Data Warehouse

How To Create Value With Recurly Data

Teams connect Recurly to their data warehouse to build dashboards and generate value for their business. Let’s dig into the capabilities Recurly exposes via their API, outline insights you can build with the data, and summarize the most common analytics environments teams are using to process their Recurly data.

Extract: What Data Can You Extract From The Recurly API?

Recurly is a subscription and billing platform used for growing recurring revenue.

To help clients power downstream analytics, Recurly offers an application programming interface (API) for clients to extract data on business entities. Here are a few example entities you can extract from the API.

  • Subscriptions
  • Plans
  • Transactions
  • Invoices
  • Coupons
  • Accounts
  • Etc.

You can visit the Recurly API documentation to explore the entire catalog of available API resources and the complete schema definition for each. As an example, here are some of the details for the sites endpoint in the Recurly API documentation.

Recurly sites API
Recurly sites API

As you think about the data you will need for analytics, don’t forget that Portable offers no-code integrations to other similar applications like Chargebee, Chargify, and Baremetrics that can be useful for comparison purposes.

Regardless of the SaaS solution you use, it’s important to find a subscription and billing platform with robust data available for analytics.

Load: Which Destinations Are Best For A Recurly ETL Pipeline?

To turn raw data from Recurly into dashboards, most companies centralize information into a data warehouse or data lake. For Portable clients, the most common ETL pipelines are:

  1. Recurly to Snowflake Integration
  2. Recurly to Google BigQuery Integration
  3. Recurly to Amazon Redshift Integration
  4. Recurly to PostgreSQL Integration
Common Data Warehouses
Common Data Warehouses

Once you have a destination to load the data, it’s common to combine Recurly data with information from other enterprise applications like Jira, Mailchimp, HubSpot, Zendesk, and LinkedIn.

From there, you can build cross-functional dashboards in a visualization tool like Power BI, Tableau, Looker, or Retool.

Develop: Which Dashboards Should You Build With Recurly Data?

Now that you have identified the data you want to extract, the next step is to plan out the dashboards you can build with the data.

As a process, you want to consume raw data, overlay SQL logic, and build a dashboard to either 1) increase revenue or 2) decrease costs.

Here are three subscription analytics dashboards you should consider as a starting point.

  1. Monthly Subscription Summary - When your clients pay via a recurring subscription, it's important to understand month-over-month trends to see how revenue is growing. There is no more important dashboard than subscription revenue over time.
  2. Referral Attribution (By Coupon Code) - For subscription platforms that offer coupon codes, they can be applied to subscriptions and invoices. What's the best way to summarize how your referral program is working? By showing the most leveraged coupon codes by frequency and revenue to understand where to double down and where to move on.
  3. Customer Revenue Summary - By breaking down revenue by customer, you can bring in transaction data, subscription data, and invoices data to understand which clients and growing and which are shrinking. This data is critical to creating a customer 360 view and can easily be joined with other data sources.

Beyond the dashboards above, replicating Recurly data into your cloud data warehouse can unlock a wide array of opportunities to power analytics, automate workflows, and develop products. The use cases are endless.

Now that we have a clear sense of the insights we can create, let’s compare the process of developing a custom Recurly integration with the benefits of using a no-code ETL solution like Portable.

Method 1: Building A Custom Recurly ETL Pipeline

To build your own Recurly integration, there are three steps:

  1. Navigate the Recurly API documentation
  2. Make your first API request
  3. Turn an API request into a complete data pipeline

Let’s walk through the process in more detail.

How To Interpret Recurly’s API Documentation

When reading API documentation, there are a handful of key concepts to consider.

Authentication

There are many common authentication mechanisms. OAuth 2.0 (Auth Code and Client Credentials), API Keys, JWT Tokens, Personal Access Tokens, Basic Authentication, etc. For Recurly, it’s important to identify the authentication mechanism and how best to incorporate the necessary credentials into your API requests.

Recurly uses basic auth for authentication. Pass your API key as the username and leave the password as an empty string.

Recurly Authentication Overview
Recurly Authentication Overview

Resources

It’s important to identify the Recurly API endpoints you want to use for analytics. Most APIs offer GET, POST, PUT, and DELETE methods; however, for analytics, GET requests are typically the most useful. At times, POST requests can be used to extract data as well.

For Recurly, the sites endpoint is a great place to get started.

Request Parameters

For each API endpoint, you would like to use for analytics, you need to understand the method (GET, POST, PUT, or DELETE) and the URL, but there are other considerations to take into account as well. You should look out for pagination mechanics, query parameters, and parameters that are added to the request path.

Some API endpoints offer pagination. For instance, when listing sites, you can set a 'limit', a 'sort', and an 'order'. To make the next call, you can use the has_more and next parameters that are returned in the response.

Recurly Pagination Overview
Recurly Pagination Overview

Some API endpoints require unique identifiers from a previous API response to be included in the URL path.

For instance, to get all accounts for a site, you need a site ID that is returned from another endpoint.

Recurly API Request Parameters
Recurly API Request Parameters

How Do You Call The Recurly API? (Tutorial)

  1. Follow the instructions above to read the Recurly API documentation
  2. Identify and collect your credentials for authentication
  3. Pick the API resource you want to pull data from
  4. Configure the necessary parameters, method, and URL to make your first request (Either with curl or Postman)
  5. Add your credentials and make your first API call. Here is an example request using curl (without real credentials):
curl -G https://v3.recurly.com/sites \
  -u api_key: \

How Do You Maintain A Custom Recurly ETL Pipeline?

Making a call to the Recurly API is just the beginning of maintaining a complete custom ETL pipeline.

Here is a getting started guide to building a production-grade pipeline for Recurly:

  • For each API endpoint, define schemas (which fields exist and the type for each)
  • Process the API response and parse the data (typically parsing JSON or XML)
  • Handle and replicate nested objects and custom fields
  • Identify which fields are primary keys and which keys are required vs. optional
  • Version control your changes in a git-based workflow (using GitHub, GitLab, etc.)
  • Handle code dependencies in your toolchain and the upgrades that come with each
  • Monitor the health of the upstream API, and - when things go wrong - troubleshoot via the status page, reach out to support, and open tickets
  • Handle error codes (HTTP error codes like 400s, 500s, etc.)
  • Manage and respect rate limits imposed by the server

We won’t go into detail on all of the items above, but rate limits are a great example of the complexity found in a production-grade data pipeline.

For rate limits, Recurly restricts the number of incoming calls you can make to 1,000 requests per minute and 400 requests per minute in your sandbox sites. In production, only calls using a GET method count towards the rate limit.

Recurly Rate Limits
Recurly Rate Limits

If you don’t respect rate limits, and if you can’t handle server responses (like 429 errors with a Retry-After header), your pipeline can break, and analytics can become out-of-date.

What Are The Drawbacks Of Building A Recurly ETL Pipeline Yourself?

You can probably tell at this point that there is a lot of work that goes into building and maintaining an ETL pipeline from Recurly to your data warehouse.

If you want less development work, faster insights, and no ongoing responsibilities, you should consider a cloud-hosted ETL solution.

Let’s walk through the setup process for a no-code ETL solution and its benefits.

Method 2: Using A No-Code Recurly ETL Solution

No-code ETL solutions are simple. Vendors are specialized in building and maintaining data pipelines on your behalf. Instead of starting from scratch for each integration. Companies like Portable create connector templates that can be leveraged by hundreds or thousands of clients.

Step-By-Step Tutorial For Configuring A Recurly ETL Pipeline

Off-the-shelf ETL tools offer a no-code setup process. Here are the instructions to connect Recurly to your cloud data warehouse with Portable.

  1. Create an account (no credit card required)
  2. Add a source - Search for and select Recurly
  3. Authenticate with Recurly using the instructions in the Portable console
  4. Select your warehouse (Snowflake, BigQuery, Redshift, or PostgreSQL) and authenticate
  5. Set up a flow connecting Recurly to your analytics environment
  6. Run your flow to replicate data from Recurly to your warehouse
  7. Use the dropdown to set your data flow to run on a cadence

What Are The Benefits Of Using Portable For Recurly ETL?

No-Code Simplicity

Start moving Recurly data in minutes. Save yourself the headaches of reading API documentation, writing code, and worrying about maintenance. Leave the hassle to us.

Easy To Understand Pricing

With predictable, fixed-cost pricing per data flow, you know exactly how much your Recurly integration will cost every month.

Fast Development Speeds

Access lightning-fast connector development. Portable can build new integrations on-demand in hours or days.

Hands-On Support

APIs change. Schemas evolve. Recurly will have maintenance issues and errors. With Portable, we will do everything in our power to make your life easier.

Unlimited Data Volumes

You can move as much Recurly data as you want without worrying about usage credits or overages. Instead of analyzing your ETL costs, you should be analyzing your data.

Free To Get Started

Sign up and get started for free. You don’t need a credit card to manually trigger a data sync, so you can try all of our connectors before paying a dime.

Stop waiting for your data.Start using Portable today.

Pioneer insights and streamline operations with data from all your business applications.

Get Started