Release Noteslink

October 2023link

The Recharge connector now supports priority-first sync for the DISCOUNT table. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Recharge's priority-first syncs fetch the most recent 15 days' worth of data from the supported tables. We are gradually rolling out this change to all existing connectors. To learn more, see our priority-first sync documentation.

September 2023link

The Recharge connector now supports priority-first sync for the following tables:

ADDRESS
ADDRESS_DISCOUNT
ADDRESS_SHIPPING_LINE
CHARGE
CHARGE_DISCOUNT
CHARGE_LINE_ITEM
CHARGE_ORDER_ATTRIBUTE
CHARGE_SHIPPING_LINE
CHARGE_TAX_LINE
CHECKOUT
CHECKOUT_LINE_ITEM
CUSTOMER
METAFIELD
ONE_TIME_PRODUCT
ORDER
ORDER_LINE_ITEM
PAYMENT_METHOD
PLAN
SUBSCRIPTION
SUBSCRIPTION_HISTORY
UTM_TAG
Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Recharge's priority-first syncs fetch the most recent 15 days' worth of data from the supported tables. We are gradually rolling out this change to all existing connectors. To learn more, see our priority-first sync documentation. We now sync the METAFIELD table using the following endpoints:
META_FIELD_CHARGE
META_FIELD_CUSTOMER
META_FIELD_ORDER
META_FIELD_STORE
META_FIELD_SUBSCRIPTION

We have added a new column value_type to the DISCOUNT table.

June 2023link

We now capture soft deletes for the PAYMENT_METHOD table. We create a new _fivetran_deleted column in the destination table, and mark the deleted rows as TRUE.

We have released pre-built, dbt Core-compatible data models for Recharge. Find the models in Fivetran's dbt hub or data models documentation. Learn more about our dbt Core integration in our Transformations for dbt Core documentation*.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

April 2023link

We have upgraded our Recharge connector from version 2021-01 to 2021-11 of the Recharge API. We have made the following schema changes:

We have the added the following new tables:
- ADDRESS_DISCOUNTS
- CHARGE_DISCOUNT
- CHARGE_ORDER_ATTRIBUTE
We have deprecated the following tables:
- CHARGE_DISCOUNT_CODE
- CHARGE_NOTE_ATTRIBUTE

We have added the following new columns to the tables below:

TABLE	NEW COLUMNS
`ADDRESS`	`payment_method_id` and `country_code`
`CHARGE`	`billing_address_country_code`, `orders_count`, and `shipping_address_country_code`
`CHARGE_LINE_ITEM`	`taxable_amount`, `tax_due`, `taxable`, `total_price`, `unit_price`, and `unit_price_includes_tax`
`CHECKOUT`	`billing_address_country_code`, `external_transaction_id_payment_processor`, and `shipping_address_country_code`
`CUSTOMER`	`tax_exempt`
`ORDER`	`billing_address_country_code` and `shipping_address_country_code`
`ORDER_LINE_ITEM`	`tax_due`, `taxable`, `taxable_amount`, `total_price`, `unit_price`, and `unit_price_includes_tax`
`PAYMENT_METHOD`	`billing_address_country_code`, `default`, and `payment_details`

We have replaced the following columns in the tables below:

TABLE	OLD COLUMN	NEW COLUMN
`ADDRESS`	`cart_note`	`order_note`
`CHARGE`	`transaction_id`	`external_transaction_id_payment_processor`
`CHARGE`	`total_weight`	`total_weight_grams`
`CHARGE`	`number_times_tried`	`charge_attempts`
`CHARGE`	`shopify_variant_id_not_found`	`external_variant_id_not_found`
`CHARGE`	`processor_name`	`payment_processor`
`CHECKOUT`	`note_attributes`	`order_attributes`
`CUSTOMER`	`has_card_error_in_dunning`	`has_payment_method_in_dunning`
`CUSTOMER`	`number_active_subscriptions`	`subscriptions_active_count`
`CUSTOMER`	`number_subscriptions`	`subscriptions_total_count`
`ONETIME`	`shopify_product_id`	`external_product_id`
`ORDER_LINE_ITEM`	`product_title`	`title`

We have deprecated the following columns from the tables below:

TABLE	DEPRECATED COLUMNS
`ADDRESS`	`country`
`CHARGE`	`billing_address_country`, `first_name`, `last_charge_attempt_date`, `last_name`, `shipments_count`, `shipping_address_country`, and `sub_total`
`CHARGE_LINE_ITEM`	`price` and `subscription_id`
`CHECKOUT`	`billing_address_country`, `buyer_accepts_marketing`, `discount_code`, and `shipping_address_country`
`CUSTOMER`	`billing_address1`, `billing_address2`, `billing_city`, `billing_company`, `billing_country`, `billing_first_name`, `billing_last_name`, `billing_phone`, `billing_province`, `billing_zip`, `processor_type`, `reason_payment_method_not_valid`, and `status`
`DISCOUNT`	`discount_type`, `duration`, `duration_usage_limit`, `once_per_customer`, and `times_used`
`ONETIME`	`recharge_product_id` and `status`
`ORDER`	`address_is_active`, `billing_address_country`, `first_name`, `last_name`, `payment_processor`, `shipping_address_country`, `shipping_date`, `shopify_customer_id`, and `shopify_id`
`ORDER_LINE_ITEM`	`price` and `subscription_id`
`PAYMENT METHOD`	`billing_address_country`

NOTE: We will re-sync all the new tables and columns to load their historical data.

March 2023link

We now capture deletes for the CHARGE and CUSTOMER tables. In order to remove the previously deleted records from these tables, trigger a full historical re-sync for these tables.

We have upgraded our Recharge connector from version 2021-01 to 2021-11 of the Recharge API. We have made the following schema changes:

We have added a new table, CHARGE_TAX_LINE, to replace the tax_lines column of the CHARGE table.
We have added a new table, PAYMENT_METHODS, to replace the PAYMENT_SOURCE table.
We have added a new table, PLANS, to replace the PRODUCT table.
We have added two new columns, purchase_item_id and purchase_item_type, to the ORDER_LINE_ITEM and CHARGE_LINE_ITEM tables.
We have renamed the following columns of the DISCOUNT table:
- applies_to_product_type to applies_to_purchase_item_type
- usage_limit to automatic_redemptions_per_customer
We have renamed the following columns of the ORDER table:
- shopify_cart_token to external_cart_token
- shopify_order_id to external_order_id_ecommerce
- shopify_order_number to external_order_number_ecommerce
We have renamed the following columns of the SUBSCRIPTION table:
- shopify_product_id to external_product_id_ecommerce
- shopify_variant_id to external_variant_id_ecommerce
We have renamed the following columns in the CHARGE_LINE_ITEM and ORDER_LINE_ITEM tables:
- shopify_product_id to external_product_id_ecommerce
- shopify_variant_id to external_variant_id_ecommerce
We have renamed the shopify_customer_id column of the CUSTOMER table to external_customer_id_ecommerce.
We have renamed the shopify_order_id column of the CHARGE table to external_order_id_ecommerce.
We have renamed the shopify_variant_id column of the ONETIME_PRODUCT table to external_variant_id_ecommerce.
We have deprecated the status column of the CUSTOMER table.
We have deprecated the subscription_id column of the ORDER_LINE_ITEM and CHARGE_LINE_ITEM tables.

For more information about the changes, see Recharge API’s changelog.

If you want to sync historical data for these columns, contact our support team.

October 2022link

We have renamed our ReCharge connector to Recharge, following Recharge's name change. This name change applies to the Fivetran dashboard and our documentation.

October 2021link

We have replaced the is_deleted column in the SUBSCRIPTION table with a new _fivetran_deleted column. We have removed the is_deleted column. Be sure to update your queries.

April 2021link

We have added the following new columns to the UTM_TAG table:

campaign
content
data_source
medium
source
term
time_stamp

We will deprecate the following columns of the UTM_TAG table after July 1, 2021:

utm_campaign
utm_content
utm_data_source
utm_medium
utm_source
utm_term
utm_time_stamp

Be sure to update your queries with the new column names before we remove the old columns.

March 2021link

We have added the following new tables:

CHECKOUT
CHECKOUT_LINE_ITEM
METAFIELD
PAYMENT_SOURCE
PRODUCT

NOTE: We use webhooks to retrieve data from the Checkouts endpoint. See Recharge's API Documentation for more information.

February 2021link

We have added the following new columns to the CUSTOMER table:

first_charge_processed_at
number_active_subscriptions
number_subscriptions

November 2020link

We now use webhooks to capture deletes for the ONE_TIME_PRODUCT, ORDER, and SUBSCRIPTION tables. We have added a is_deleted column to the three tables to track the deleted records.

We have deprecated the ANALYTICS_DATA table. We now sync this data to the UTM_TAG table.

August 2020link

We now use webhooks to sync record updates in the CHARGE, ORDER, and SUBSCRIPTION tables.

We have added a new table, ONE_TIME_PRODUCT.

July 2020link

We have added the following columns to the CHARGE table:

last_charge_attempt_date
retry_date
number_times_tried
error
error_type
shopify_variant_id_not_found

We have replaced the ANALYTICS_DATA table with the UTM_TAG table. We will deprecate the replaced table after November 1, 2020. Be sure to update your queries with the new table name before we remove the old table.

We have removed the _fivetran_deleted column from the SUBSCRIPTION table.

May 2020link

We have added a new column, _fivetran_deleted, to the SUBSCRIPTION table.

We have added a new column, _next_charge_scheduled_at, to the SUBSCRIPTION ATTRIBUTE table.

April 2020link

We now sync analytics data from the CUSTOMER, CHARGE, and SUBSCRIPTION tables into the ANALYTICS_DATA table.

January 2020link

We have added the following columns to the CHARGE table:

email
has_uncommited_changes
processor_name
total_refunds
transaction_id

December 2019link

We have added the following columns to the CUSTOMER table:

has_card_error_in_dunning
has_valid_payment_method
reason_payment_method_not_valid

June 2019link

Added price, sku and grams columns to the ORDER_LINE_ITEM table.

January 2019link

We have removed the restrict_by_email column from the DISCOUNT table.

May 2018link

We have corrected the way our system interprets timestamps. The Recharge API produces timestamps that look like 2018-01-01T00:00:00. Previously, we interpreted these timestamps as UTC, when they were actually Eastern Time (ET). This meant that all destination timestamps were off by 4 or 5 hours, depending on daylight savings. All timestamps are now correctly converted from ET to UTC before they arrive in your destination. Note that there is still one hour each year where the timestamp is ambiguous due to daylight savings time. Recharge is working on a fix for this in their API.

April 2018link

The Recharge API sometimes returns non-number values in the price column of the ADDRESS_SHIPPING_LINE table, so this field is now a STRING.

The note_attribute column in the CHARGE_NOTE_ATTRIBUTE table can now contain nested JSON values. For example:

[
  {
    "name": "How did you hear about us?",
    "value": "Social_media_ad:"
  },
  "some attribute"
]
content_copy