STEM University — Prove skills by building

Your Work

Ten canonical segment recipes. Each recipe is a population field over the event stream; the Segment Builder encodes a container choice, include/exclude option, and (sometimes) a sequence operator. The math probes ask the population size; the structural probes ask the Builder configuration.

Date range

Recipe populations (math)

Each recipe is a set built over the events in your DR. Submit the size of the resulting set (or, for purchaser revenue, the sum).

Purchasers — |{u : ∃ order}|

Non-Purchasers — |U \ Purchasers|

Single-Page Visits — PV(v)=1

Multi-Page 1-Visit Visitors — 1 visit, PV>1

Strictly Organic orders — evar_1=organic

Strictly Paid orders — evar_1∈{paid_search, email}

Checkout Fallout — PV>0 ∧ Orders=0

Purchaser revenue — Σ price · 1[order]

Segment Builder rules

Recipe #1 — Purchasers

Container:

Orders operator:

Recipe #2 — Non-Purchasers

Drop-zone option used to flip Purchasers → Non-Purchasers:

Recipe #3 — Single-Page Visitors (two-container template)

First container (count single-page visits):

Second container (drop multi-visit visitors):

Second container option:

Recipe #6 — Pre-Purchase Activity

Logic operator between PV and Order:

Sequence type:

Recipe #9 — Potential Bots

Where do you place the Exclude option?

Recipe #7 — Strictly Organic (channel bundle)

Logic between unpaid marketing channels:

Evaluation

Practice checks are unlimited and don’t count toward your grade. Final submit is one-time and generates your certificate.

Practice the workspace, ask Dr. Okoye anything, and submit when you're ready. The grade lives in the workspace, not the chat.