Finding Matching Sequences
For Product Viewed > Added to Cart > Payment Completed, zinzu finds two completed sequences for C-101. Each occurrence has a separate Sequence ID.
| event_owner | sequence_id* | timestamp | event_name | event_data |
|---|---|---|---|---|
| C-101 | S-1 | 10:00:00 | Product Viewed | { "customer_id": "C-101", "activity_time": "10:00:00", "action": "Product Viewed" } |
| C-101 | S-1 | 10:01:00 | Added to Cart | { "customer_id": "C-101", "activity_time": "10:01:00", "action": "Added to Cart" } |
| C-101 | S-1 | 10:03:00 | Payment Completed | { "buyer_id": "C-101", "payment_time": "10:03:00", "status": "Completed" } |
| C-101 | S-2 | 11:00:00 | Product Viewed | { "customer_id": "C-101", "activity_time": "11:00:00", "action": "Product Viewed" } |
| C-101 | S-2 | 11:02:00 | Added to Cart | { "customer_id": "C-101", "activity_time": "11:02:00", "action": "Added to Cart" } |
| C-101 | S-2 | 11:05:00 | Payment Completed | { "buyer_id": "C-101", "payment_time": "11:05:00", "status": "Completed" } |
C-202 has no completed match because its timeline contains only Product Viewed.
Reading This Example
event_owner: The customer whose timeline is analyzed.
sequence_id: Groups records belonging to one sequence.
timestamp: When the action occurred.
event_name: The matched User Defined Event.
event_data: The source record’s attributes as key/value pairs, preserving their original column names.
* Sequence IDs and timestamp values are simplified for illustration. This is a simplified results example.