Also replying since I wrote this up :)

- activity_id : a unique identifier for the row

- activity : the type of activity (eg 'page_view')

- timestamp : time the activity happened

- customer : the unique customer identifier

Metadata columns

  Three columns for any info we'd like to add to an activity. Eg for a purchased product activity it could be product name. 

 - feature_1
 - feature_2
 - feature_3

 - revenue_impact : the amount of money related to this activity. A completed order activity would have this
 - link : a hyperlink related to the activity ('ticket submitted' might have a link to the ticket in Zendesk)

Additional customer identifier - source and source id are used when you're not entirely sure who the customer is. For example, a 'page view' activity wouldn't know the actual customer, but might have a unique identifier. So the source could be 'segment.io' and source_id could be their generated uuid

- source

- source_id

Activity, Customer, Time, Activity, 3 features, Revenue impact. source and source_id (for identity resolution) and a couple of meta data columns.

You can see some example transformations here: https://docs.narrator.ai/docs/by-data-source