Skip to main content
Version: v2


Sync Expectations

The following table describes the sync behavior of Fullstory events to Snowflake.

DestinationSync IntervalUpdate Window*Relevant TimestampsSetup Guide
SnowflakeApproximately processed_time rounded to the next hour + 1 hour99% stable within 3 hoursevent_time
Snowflake Help Doc

* Update Window: These are observed aggregates and may vary based on the specifics of the data capture for your site or app.

Events Table Schema

The following table contains the schema for the Fullstory events in Snowflake. For information on the data types, see the Snowflake documentation.

event_idVARCHARThe unique identifier for the event.
event_timeTIMESTAMPThe time in UTC that the event occurred.
processed_timeTIMESTAMPThe time in UTC that the event was processed by Fullstory's servers.
updated_timeTIMESTAMPThe time in UTC that event was updated in the database. Set via SYSDATE when merging.
device_idBIGINTThe device ID as defined in the base event model.
session_idBIGINTThe session ID as defined in the base event model.
view_idBIGINTThe view ID as defined in the base event model.
event_typeVARCHARThe type of this event.
event_propertiesVARIANTA json object containing the associated event properties.
source_typeVARCHARThe source type of the event.
source_propertiesVARIANTA json object containing the associated source properties.

Querying the Events Table

To demonstrate how to query the events table, the following example shows how to count the number of rage clicks broken down by browser and URL for a single day.

source_properties:user_agent.browser::string as browser,
source_properties:url.path::string as path,
count(1) as rage_clicks
date(event_time) = '2024-01-01'
AND event_type = 'click'
AND event_properties:fs_rage_count::int > 0
rage_clicks DESC;

Analyze with DBT

Fullstory provides a DBT package to help you get started with Snowflake. The package includes models for Fullstory events, sessions, and users.