Recharge is a subscription platform which integrates with Shopify and BigCommerce, and allows you to manage and maintain subscription services for your customers.
By integrating Recharge with Dotdigital, you can sync your customers and subscription information, powering:
targeted campaigns to drive subscription renewals or upgrades.
deep segmentation to identify those with lapsed, paused, or recently cancelled subscriptions for re-engagement.
highly personalised messaging to help increase retention and revenue.
Subscription data from Recharge is stored in an Insight data collection in Dotdigital.
Learn more about working with Insight data:
Before you start
Things you need to know:
Your account and user profile must have permission to access the integrations area.
Learn more in Manage user access and permissions.
Install the integration
In Dotdigital, go to Connect > Integrations.
In the left side panel, under SHOW, select Self-serve.
For Recharge, select ADD.
In the side panel, select INSTALL.
For Recharge authentication, select AUTHENTICATE, then enter your Recharge credentials to connect your accounts
Select NEXT.
Expand the Sync type drop-down menu and choose from:
Sync all contacts
Create new contacts in Dotdigital for contacts synced from Recharge that don’t already exist.Update existing contacts
Only sync updated subscription data for contacts that already exist in Dotdigital.
Select FINISH.
Data structure
The subscription data we sync from Recharge is stored as a contact-scoped Insight data collection with the below schema.
Field name | Type | Description |
ID | integer | Unique identifier for the subscription. |
address_id | integer | Unique identifier for the address the subscription is associated with. |
customer_id | integer | Unique numeric identifier for the customer the subscription is tied to. |
status | string | The status of the subscription. |
cancellation_reason | string | Comments for cancellation. Max 1024 characters |
cancelled_at | datetime | Time of cancellation. In UTC, ISO 8601 format. |
purchase_date | datetime | Time subscription was created. In UTC, ISO 8601 format. |
updated_at | datetime | The date time at which the purchase_item record was last updated. In UTC, ISO 8601 format. |
expiration_date | numeric | The number of charges until subscription expires. |
currency | string | The currency that the subscription is charged in. |
order_interval | object |
|
order_interval.frequency | integer | The number of units (specified in order_interval_unit) between each order. |
order_interval.unit | string | The frequency unit used to determine when a subscription’s order is created. Possible values:
|
order_interval.day_of_week | integer | The set day of the week order is created. |
products | array | The products included in the order. |
products.name | string | The name of the product in a store’s catalog. |
products.external_ID | object | An object containing the product ID as it appears in external platforms. |
products.variant_ID | object | An object containing the variant ID as it appears in external platforms. |
products.variant_title | string | The name of the variant in the store catalog. |
products.price | numeric | The price of the item before discounts, taxes, or shipping. |
products.sku | string | Unique identifier for the product. |
products.qty | numeric | Number of items in the subscription. |
next_purchase_date | datetime | Date of the next charge for the subscription. In UTC, ISO 8601 format. |
has_queued_charges | Boolean | Value is true if there is queued charge. Otherwise, false. |
is_prepaid | Boolean | Value is set to true if it is a prepaid item. |
is_skippable | Boolean | Value is set to true if it is not a prepaid item. |
is_swappable | Boolean | Value is set to true if it is not a prepaid item, and if in customer portal settings swap is allowed for customers. |
max_retries_reached | Boolean | Retrieves true if a charge has a max retries reached error. Otherwise, retrieves false. |
Properties | object | A list of line item objects containing information about the subscription. Custom key-value pairs can be recorded here to appear on the connected queued charge after the order is processed. |