Skip to main content
Version: v2


Sync Expectations

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

DestinationSync IntervalUpdate Window*Relevant TimestampsSetup Guide
RedshiftApproximately processed_time rounded to the next hour + 1 hour99% stable within 3 hoursevent_time
Redshift 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 Redshift. For information on the data types, see the Redshift documentation.

event_idVARCHAR(MAX)The unique identifier for the event.
event_timeTIMESTAMPTZThe time in UTC that the event occurred.
processed_timeTIMESTAMPTZThe time in UTC that the event was processed by Fullstory's servers.
updated_timeTIMESTAMPTZThe 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_typeVARCHAR(MAX)The type of this event.
event_propertiesSUPERA json object containing the associated event properties.
source_typeVARCHAR(MAX)The source type of the event.
source_propertiesSUPERA 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::varchar as browser,
source_properties.url.path::varchar as path,
count(1) as rage_clicks
date(event_time) = '2024-01-01'
AND event_type = 'click'
AND event_properties.fs_rage_count > 0
rage_clicks DESC;

Analyze with DBT

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