Common table expressions allow you define tables at the top of your query rather than in-line as sub-queries. Playbook reports use common table expressions to help you format your data to each query. These additional details are noted in the guide for each report. Some reports only require an events table, while others might require additional information.
One column should be a user_id, which matches to the user_id in the first table one column should be the event_name, which is how you identify which action a user took and one column should be called occurred_at, and is a timestamp of when this event took place. Events can be logins, purchases, clicks, screen views, or any other action taken by users. This table should include on row per event. Finally, this table should have one row per user. This represents the first time that user signed up, their first purchase, or any other initializing event. The second column should be an activated_at timestamp. One column should be a user_id, which is a unique identifier for that user. This table is expected to have one row per user (or customer or account), and typically has two columns. The people table can represent users, customers, accounts, or any other type of identity. Most reports use only these two tables, one for people and one for events. The Playbook reports are built on top of a common schema of people and events. The three sections below outline what data is required, how to format reports to fit that data, and how to edit reports to make them compatible with different types of databases. This document outlines how to use Mode Playbook with your data.
0 kommentar(er)
