Define the matching rule
Synthetic click CLK26 belongs visitor V26 at 10:00. Local credit candidates require same visitor and event time from 10:00 inclusive to 10:05 exclusive. E1 V26 at 10:04, E2 V26 at 10:05 and E3 V27 at 10:03. This is a local attribution convention, not a platform default or evidence the click caused the conversion.
| Event | Visitor/time | Matches |
|---|---|---|
| E1 | V26/10:04 | Yes |
| E2 | V26/10:05 | No:time |
| E3 | V27/10:03 | No:identity |
Check identity and event time
- Match visitor keys
- Compare event time with click window
- Propose CLK26/E1 link
- Keep E2/E3 uncredited by this click
Missing identity or timestamp leaves matching unresolved; do not fill them from the nearest row.
How many events match CLK26?
Show the worked answer
One, E1. E2 is exactly at the excluded end; E3 is within time but a different visitor.
Record matching and unmatching cases
| Case | Decision or result | Reason |
|---|---|---|
| Treat 10:05 as inclusive | Reject under local rule | End excluded |
| Match by time only | Reject E3 link | Visitor differs |
The output is a policy-based credit candidate, not causal lift or ROI. Retain click/event identities and the rule revision.