ReCharge Release Notes – Fivetran Support Portal

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"
]