Service template
Lifecycle: a behavioral audience
Define separate audiences from lead and checkout events on user-life days 14–60, excluding days 0–13. Confirm the starting event and zero-based day boundaries.
Request a first consultationBusiness result
Deduplicated audiences with verified eligibility and overlap
- Next step
- Define an audience
- Working output
- SQL / notebook
- Unit of analysis
- User ID × qualifying event × days since a defined starting event
- Decision owner
- To agree
Audience eligibility and identity
- Define the starting event, included population and inclusive time boundaries.
- Specify inclusion, exclusion, identity resolution and overlap rules.
- Check aggregate audience size and permission to use identifiers before delivery.
Acceptance checks
- Starting event, timezone and inclusive day boundaries are explicit.
- Each user appears once; exclusions, overlaps and authorized delivery are checked.
Deliverables
- An audience selection rule with size and overlap checks
- Read-only queries or notebook, parameters, results and a reproducible analysis dataset.
- A dated finding with source period, cutoff, methods, limitations and next action.