Simon Data provides access to the underlying tables that are used within our results product for use within your internal BI infrastructure. This is currently only available through Snowflake Data Sharing.

Please note, this product is presented as a pre-alpha product that is for clients to explore and provide feedback to shape further development. It is recommended that clients keep Simon aware of any use.

Tables

Results Product Source Tables

Customer

• Latest version of the Simon customer table that backs the Segment builder
• Currently this is updated once a day at night
• Schema
  • Simon ID
  • Email
  • All customer fields for segmentation and content

Identity

• Batch identity table that creates consistent Simon IDs per customer across join keys (e.g. user_id)
• This is used to be able to join a customer across client_id, email and users_ids
• Job is implemented as full batch job and Simon IDs will not necessarily be consistent from one run to the next
• Schema
  • Native ID
  • Native identifier (e.g. email, client_id, user_id)
  • Simon ID

Event tables

• Names match the events configured for use within Results. These are the event that can be used as starts, goals and milestones
• Updated on a daily basis
• Flow_actions - Log of all actions taken by Simon
• Other events specific to clients (e.g. Sendgrid sends, purchase, etc.)
• Schema
  • Native ID
  • Native identifier
  • Timestamp
  • Event
  • Event properties (can be 0 to n)

Metadata tables

These tables are under active development. May see some tables labeled Alpha, which can help for use with joining.
###Metadata_simon_flows

• Provides configuration information on each flow
• Schema
  • Campaign_ID
  • Campaign_name
  • Journey_name
  • Current_status
  • Campaign_category
  • Holdout_size
  • Has_experiment
  • Variant_id
  • Variant_name
  • Launch_date
  • Launched_at
  • Segment_id
  • Segment_name
  • Ended_at
  • Created_at
  • Updated_at

Campaign_action_metadata

• Join table showing the details behind any flow action (e.g. integration)
• Campaign actions are the flow actions built in the flows product. Each flow action maps one-to-one with an action type (e.g. triggered send) and integration (e.g. SendGrid)
• Schema
  • Campaign_action_id
  • Campaign_id
  • Integration_name
  • Action_name
  • Created_at
  • Updated_at