Release Notes
September 2023
We have added the collector_tstamp column as a part of the composite primary key of the EVENT table. The new composite primary key is a combination of the collector_tstamp and event_id columns.
We have added a new column, collector_tstamp, to the UA_PARSER_CONTEXT and [CUSTOM_CONTEXT] tables. We have also added the collector_tstamp column to the composite primary key of the two tables. The new composite primary key is a combination of the collector_tstamp and event_id columns.
We are gradually rolling out these changes to all existing connections.
April 2022
We have deprecated the dvce_tstamp field. Make sure that your queries don't contain this field.
March 2022
We have added a new table, BAD_EVENT, that stores the events that do not conform to the Snowplow Canonical Event format.
October 2020
We now support two new fields, derived_tstamp and true_tstamp. See Snowplow Analytics' documentation for more information about timestamps.
We have replaced the dvce_tstamp field with the dvce_created_tstamp field. We will discontinue the replaced field after January 10, 2021. Be sure to update your queries with the new field name before we remove the old field.
We now support the IP anonymization enrichment. See our Snowplow documentation for more information.
We now support Snowplow JavaScript Tracker 2.15.0.
We have added a new column, mac_address, to the _EVENT table.
We have added two new fields, mkt_clickid and mkt_network, to the _EVENT table to support Campaign attribution enrichment 1-0-1. The two fields store the click ID and the network responsible for the click respectively.
August 2020
You can now exclude the UA_PARSER_CONTEXT table from the sync. Deselect the table from the Schema tab on your connector details page.
July 2020
We have added two new fields, refr_domain_user_id and refr_dvce_tstamp, to the _EVENT table to facilitate Cross-Domain Tracking. These two fields store the _sp query parameter values.
We now support Cross-Domain Tracking.
You can now configure your Snowplow connector using the Fivetran REST API. This feature is in BETA and is available only for Standard and Enterprise accounts.
June 2020
You can now add multiple Snowplow connectors per destination.
May 2020
We have changed the data type of the user_fingerprint field from LONG to STRING.
We have added a new field, data, in the _EVENT table.
April 2020
We now support POST requests for all Snowplow connections.
March 2020
We have changed the data type of the following fields in the _EVENT table:
| Field Name | Old Data Type | New Data Type |
|---|---|---|
ti_quantity | INT | DOUBLE |
domain_sessionidx | INT | STRING |
tr_total | BIGDECIMAL | STRING |
tr_tax | BIGDECIMAL | STRING |
tr_shipping | BIGDECIMAL | STRING |
ti_price | BIGDECIMAL | STRING |
se_value | BIGDECIMAL | STRING |
September 2018
We have added support for UA Parser Enrichment.