Enrich Stripe with data from your warehouse to create, manage, and drive revenue analysis from your customers, products, prices, subscriptions, and invoices resources.
By combining customer data with subscription data from Stripe, you can derive insights into the most common user actions that turn free accounts into paid ones. Additionally, you can figure out which accounts are at risk of churning when you see little to no activity in paid accounts, allowing you to proactively reach out to at-risk customers before the churn.
Check out our playbook and blog post to learn how to automate usage-based billing to streamline your finance operations.
A Quote is a way to model prices that you'd like to provide to a customer. Once accepted, it will automatically create an invoice, subscription or subscription schedule.
Go to the Destinations overview page and click the Add destination button. Select Stripe and click Continue. You can then authenticate Hightouch to Stripe with an API key.
You can retrieve your an API key by following these steps:
Once you've set up your Stripe destination and have a model to pull data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview page and click the Add sync button to begin. Then, select the relevant model and the Stripe destination you want to sync to.
Your sync configuration options depend on the Stripe object you are syncing to:
You can sync columns from your source to Stripe default and custom fields. If you send data for a custom field that doesn't exist, Hightouch adds the field and automatically detects its type.
Refer to the inline mapping docs to see an example of how to map nested objects like a customer's shipping address.
The delete behavior defines how the sync behaves when the Hightouch sync engine recognizes that a record has been removed from your source. The Stripe integration only supports deletions in Upsert mode.
You can sync columns from your source to Stripe default and custom fields. If you send data for a custom field that doesn't exist, Hightouch adds the field and automatically detects its type.
Refer to the inline mapping docs to see an example of how to map nested objects like a products's metadata.
The delete behavior defines how the sync behaves when the Hightouch sync engine recognizes that a record has been removed from your source. The Stripe integration only supports deletions in Upsert mode.
You can sync columns from your source to Stripe default and custom fields. If you send data for a custom field that doesn't exist, Hightouch adds the field and automatically detects its type.
Refer to the inline mapping docs to see an example of how to map nested objects like a price's recurring object.
You can sync columns from your source to Stripe default and custom fields. If you send data for a custom field that doesn't exist, Hightouch adds the field and automatically detects its type.
Refer to the inline mapping docs to see an example of how to map nested arrays like a subscription's items.
Hightouch can perform a reference look-up to associate a subscription to a customer. After selecting the Customer ID Stripe field to map, a reference input appears. Similar to the Customer sync type, Hightouch can conduct a look-up using a Customer Email. Hightouch then sends the respective Customer ID in the request to Stripe.
If you select Customer ID, a look-up is not required.
The delete behavior defines how the sync behaves when the Hightouch sync engine recognizes that a record has been removed from your source. The Stripe integration only supports deletions in Upsert mode.
You can sync columns from your source to Stripe default and custom fields. If you send data for a custom field that doesn't exist, Hightouch adds the field and automatically detects its type.
Refer to the inline mapping docs to see an example of how to map nested objects like an invoice's customer address object.
Hightouch can perform a reference look-up to associate an invoice to a customer. After selecting the Customer ID Stripe field to map, a reference input appears. Similar to the Customer sync type, Hightouch can conduct a look-up using a Customer Email. Hightouch then sends the respective Customer ID in the request to Stripe.
If you select Customer ID, a look-up is not required.
The delete behavior defines how the sync behaves when the Hightouch sync engine recognizes that a record has been removed from your source. The Stripe integration only supports deletions in Upsert mode.
You can sync columns from your source to Stripe default and custom fields. If you send data for a custom field that doesn't exist, Hightouch adds the field and automatically detects its type.
Refer to the inline mapping docs to see an example of how to map nested arrays like invoice items.
Hightouch can perform a reference look-up to associate an invoice item to a customer. After selecting the Customer ID Stripe field to map, a reference input appears. Similar to the Customer sync type, Hightouch can conduct a look-up using a Customer Email. Hightouch then sends the respective Customer ID in the request to Stripe.
If you select Customer ID, a look-up is not required.
The delete behavior defines how the sync behaves when the Hightouch sync engine recognizes that a record has been removed from your source. The Stripe integration only supports deletions in Upsert mode.
Behavior
Description
Do nothing
Keep the invoice item in Stripe
Delete the Stripe record
Remove the invoice item from Stripe.*
*Deletion is only supported if the associated invoice item is not attached to an invoice or if it's attached to a draft invoice, otherwise, Hightouch will do nothing to the existing invoice item in Stripe.
You can sync columns from your source to Stripe default and custom fields. If you send data for a custom field that doesn't exist, Hightouch adds the field and automatically detects its type.
Refer to the inline mapping docs to see an example of how to map nested objects like a quote's computed object.
The delete behavior defines how the sync behaves when the Hightouch sync engine recognizes that a record has been removed from your source. The Stripe integration only supports deletions in Upsert mode.
Some Stripe object types have conditionally required fields based on other field values. You may receive Stripe API errors if the data you are syncing is incorrectly structured or if expected data is missing. We strongly recommend using Stripe's API documentation as reference when creating your Hightouch models and sync configurations.
Hightouch provides complete visibility into the API calls made during each of your sync runs. We recommend reading our article on debugging tips and tricks to learn more.