Successor draft v5 · based on v4

Customer events

Owned by Customer Analytics · 3 contributors

Draft work state

Saving, Data checks, and readiness are independent. Each check belongs to one exact saved revision.

Persistence Revision 2 is clean

Last saved by Maya Anders.

Data checks Data checks current

Revision 2 was checked using 10,000 sampled rows.

Readiness Ready for impact review

Revision 2 is saved and its required checks are current.

Revision 2 · saved by Maya Anders · 2026-07-26 00:01 UTC

Sources and retained attributes

Inspect each qualified source, its schema, and representative rows before changing semantic mappings.

main.customer360.customer_event_stream

Customer actions across web, mobile, store, and partner channels

Query access 9 schema columns 128 stored preview rows

Schema for main.customer360.customer_event_stream
Column	Type	Description
`customer_id`	STRING	Customer entity identifier
`event_time`	TIMESTAMP	Event occurrence time
`event_id`	STRING	Stable deterministic event tie-breaker
`event_name`	STRING	Source event name
`channel`	STRING	Interaction channel
`order_id`	STRING	Related order, when available
`page_url`	STRING	Normalized page path
`payment_status`	STRING	Payment outcome
`page_action`	STRING	Action performed on the page

Stored representative rows from the last successful source inspection
`customer_id`	`event_time`	`event_id`	`event_name`	`channel`	`order_id`	`page_url`	`payment_status`
c_00001	2026-07-13T21:41:35.721Z	evt_00001	product_viewed	web	—	/products	—
c_00002	2026-07-13T21:50:35.721Z	evt_00002	add_to_cart	partner	—	/cart	—
c_00003	2026-07-13T21:59:35.721Z	evt_00003	checkout_started	store	o_00015	/checkout	—
c_00004	2026-07-13T22:08:35.721Z	evt_00004	checkout_completed	mobile	o_00022	/checkout/complete	paid
c_00005	2026-07-13T22:17:35.721Z	evt_00005	checkout_completed	web	o_00029	/checkout/complete	captured
c_00006	2026-07-13T22:26:35.721Z	evt_00006	order_viewed	partner	o_00036	/account/orders	—
c_00007	2026-07-13T22:35:35.721Z	evt_00007	support_opened	store	o_00043	/support	—
c_00008	2026-07-13T22:44:35.721Z	evt_00008	refund_requested	mobile	o_00050	/account/orders/refund	refund_pending

Retained attributes

Choose source fields that Analyses may group, filter, or explain without making them Events.

Event Vocabulary

10 Events

Reusable row-local definitions of the business Events this model recognizes.

Product viewed

Conditions

event_name = product_viewed

Data check 31% of sampled rows matched

Current for revision 2.

Added to cart

Conditions

event_name = add_to_cart

Data check 12% of sampled rows matched

Current for revision 2.

Checkout started

Conditions

page_action = checkout_start

Data check 7.8% of sampled rows matched

Current for revision 2.

Checkout completed

Conditions

event_name = checkout_completed AND payment_status is one of paid,captured

Data check 19.4% of sampled rows matched

Current for revision 2.

Order viewed

Conditions

event_name = order_viewed

Data check 9.4% of sampled rows matched

Current for revision 2.

Support opened

Conditions

event_name = support_opened AND page_action = open_help

Data check 3.2% of sampled rows matched

Current for revision 2.

Refund requested

Conditions

event_name = refund_requested

Data check 1.1% of sampled rows matched

Current for revision 2.

Payment failed

Conditions

payment_status = failed

Data check 1.9% of sampled rows matched

Current for revision 2.

Order cancelled

Conditions

event_name = order_cancelled

Data check 0.7% of sampled rows matched

Current for revision 2.

Partner interaction

Conditions

channel = partner

Data check 25% of sampled rows matched

Current for revision 2.

Journey Profiles

1 Profile

Reusable entity identity, deterministic ordering, and optional inactivity boundaries.

Revision 5

Data checks and review

Run checks against the exact saved revision, then review concrete impact before publication.

Recorded facts

10,000 sampled rows checked

Current evidence for draft revision 2.

94% matched at least one Event

Coverage is an observation; Pathfinder does not invent an acceptability threshold.

3.4% matched multiple Events

Overlap is legal and remains visible as concrete evidence.

Impact handoffReady for impact review

Revision 2 is saved and its required checks are current.