Integrating with Stripe

When you connect to Stripe, you will unlock all of your customer, trial, subscription, charge and invoice data. It gives you the ability to craft highly personalized and relevant messages across the customer journey and unleashes powerful data visualization and segmentation.

Included are templates for Audiences, Dashboards, Reports and Playbooks to help you get started. The templates cover everything from SaaS analytics to playbooks that help onboard and welcome new customers.

Stripe prerequisites

This integration process requires having Stripe account which you have the authority and access credentials, including a restricted API key.

Ortto can connect to one Stripe account at a time. To connect to another Stripe account, disconnect and delete the data-source for the current Stripe account.

Set up your Stripe restricted API key

A restricted API key is required when connecting your Stripe account to Ortto.

When you setup the Stripe data source you will be asked for an API key. There are two types of API keys in Stripe:

  • Standard keys and

  • Restricted keys.

We recommend that customers setup a restricted key which offers greater security and requires only the needed scope of permissions.

To create a restricted API key in Stripe:

  1. Login to Stripe.

  2. Navigate to Developers  API Keys.

  3. On the API keys tab, click Add API Key.

  4. Under Restricted keys, click Create restricted key,

  5. Give the key a memorable name.

  6. Set all of the permission to Read except the All webhook resources which MUST be set to Write for the data source to function correctly.

    06
  7. Click Create Key and you will be shown the API key you need to use for your integration with Ortto.

Connecting to Stripe

The Stripe data source is a read only data source. We will not write anything back to Stripe. We require write access for web hooks in order to create the required web hook for the integration.

To connect to Stripe:

  1. On the Data sources page, click New data source.

  2. Under Payments or All data sources, select Stripe, then Get started.

  3. Enter your restricted API key

  4. Now, select your desired choice for Data retention to either:

    • store only the last 90 days of activity data, or

    • select the time frame for the data stored, and the activities which will be stored.

      It is recommended to set the data retention limits while setting up the data source. Updating the data retention limits in the future will require a resync of the data source, which may affect multiple audiences and campaigns within the CDP.

      • Select Advanced options to:

    • Choose which CDP fields can be modified from the Stripe data source, or

    • Choose not to modify CDP data fields that already have a value.

  5. Click Connect to import and synchronize data from Stripe.

  6. After the sync completes, a summary of the sync will appear click Done.

Your Ortto account is now connected with Stripe.

Depending on the amount of records in your Stripe account the initial sync may take several hours. You can view the state of the connection on the data source screen.*

Webhook limitations in Stripe

Stripe supports up to 16 webhooks. In the unlikely case you are using all of your web hooks you will need to remove existing web hooks before being able to complete the connection process. Ortto requires 1 available Stripe webhook to function.

How is the data merged into Ortto

Data is merged from Stripe to Ortto on the initial connection and subsequently, when an event occurs within Stripe.

When a person is added from the Stripe data synchronization, they are subscribed to receive email communications. No change is made to the person’s subscription to SMS notifications.

Initial data sync

People details for the Stripe customers, including the customer fields in Stripe, subscriptions and invoice data are merged into the Ortto CDP.

Ortto activities store data for each trial, subscription, charge and invoice event.

Ongoing data merge

Stripe data is merged in real time (synchronously) to Ortto.

Resynchronizing data

Stripe data is resynchronized when the data source is reconnected and when the data retention limits are adjusted. A resync of the Stripe data may affect the audiences and campaigns within the CDP by resetting the attributes for the person, and activities. Causing a person to potentially re-enter an audience, or campaign within the CDP.

A data resync may reset a person’s Email permission attribute to subscribed after they have unsubscribed from receiving email communications.

What does the data source add to my account?

The Stripe data source adds:

  • Stripe customer records and their associated fields to your CDP (known as people or contacts in Ortto).

  • Stripe activities from the last 90 days including trials, subscriptions, transactions and invoices. In some cases, however, it may be necessary to store an activity and its attribute data for longer. Therefore, Ortto provides a mechanism for customers on Business and Enterprise plans to opt-in to selectively store their activity data for longer. Learn more about data retention under Configuring data retention.

  • Templates for:

    • Audiences, based on a subscription business model (these can be removed where they are not relevant)

    • Playbooks and journeys

    • Reports

    • Dashboards, both Performance and SaaS metrics.

  • The ability to use Liquid syntax in campaign messages to personalize your messages using merge tags for Stripe person fields and activity attributes. Learn more about using Liquid syntax under Personalizing campaign content with Liquid.

Deleting a Stripe data source connection will not remove the current entries in the CDP for people or activities that were merged from that Stripe connection.

Stripe activities

Once you have integrated Stripe with Ortto a number of relevant Stripe activities and attributes are added to Ortto.

Managing connected data sources

Once you have connected at least one data source to your Ortto account, you can manage the configured data sources through the Data sources page.