Schema for customer and event table

[vishnuvvn]

Summary

Do you have a list of columns required for both customer and event table?

[rblinder]

Hi Vishnuvvn,
Thank you for reaching out and for using LTVision!

The Customer Table is a user-level dataset that defines the Day 0 for each user who has engaged with the business. This marks their initial point of interaction, or anchor event, such as installing the app or making their first purchase. In our dataset, the anchor event is first_app_open.

At a minimum, the Customer Table should include:

• UserID: A unique identifier for each user (in "string" format).

• Time of the Event: The timestamp of the anchor event (in datetime format: yyyy-MM-dd HH:mm:ss).

The Event Table documents all transaction-level, revenue-generating events associated with the advertising unit. This table records details about each event but excludes rows already represented in the Customer Table.

Each Event Table entry must include:

• UserID: A unique identifier for each user (in "string" or "object" format).

• Event Name: The name of the event (in "string" format).

• Time of the Event: The timestamp of the event (in datetime format: yyyy-MM-dd HH:mm:ss).

• Purchase Value: The revenue generated from the event (in "int" or "float" format).