Report delivered and unique actions with measurement limits
See this course’s project requirements
An unsent fictional two-message campaign with a permission/withdrawal ledger, preference segments, useful message copy, accessible action and opt-out QA, send-calendar holds and a privacy-aware delivered/unique-action review.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Save four-record permission ledger and policy/jurisdiction boundary; include the original-case decision evidence and a separate changed-case result.
- Save segment rules and excluded reasons by ID; include the original-case decision evidence and a separate changed-case result.
- Save two original unsent messages with clear opt-out placeholder; include the original-case decision evidence and a separate changed-case result.
- Save paper QA findings and hold actual send-readiness claim; include the original-case decision evidence and a separate changed-case result.
- Save revised calendar and exclusions with no auto-send action; include the original-case decision evidence and a separate changed-case result.
- Save permission/segments/copy/QA/calendar/metrics campaign packet; include the original-case decision evidence and a separate changed-case result.
Review and revise
Use these criteria to check your work and choose what to improve.
- The final packet uses the supplied task-specific constraints and all six records agree.
- Every result can be traced to an identifier, input, calculation or stated decision rule.
- Changed-case practice updates dependent records and keeps holds or uncertainty visible.
- The packet states the learner role, authority boundary and specific next verification needed before real work.
Want more background?
The idea in everyday life
Original fictional workplace practice; paper or a local document is sufficient. The rules and records below are supplied for this exercise, not asserted universal workplace policy. Hazelwood fictional report:100 attempted,5 bounced,95 delivered. 20 click events from 12 unique IDs; 3 of12 flagged automated/uncertain,9 human-verified practice actions. 70 reported opens may include privacy prefetch; 8 new withdrawals. This data is provided, no real tracking performed.
Campaign metrics need defined denominators, unique people and known tracking limits; automated opens/clicks are not guaranteed human intent or verified learning outcomes.
Report delivered and unique actions with measurement limits — worked practice
Campaign metrics need defined denominators, unique people and known tracking limits; automated opens/clicks are not guaranteed human intent or verified learning outcomes.
Hazelwood fictional report:100 attempted,5 bounced,95 delivered. 20 click events from 12 unique IDs; 3 of12 flagged automated/uncertain,9 human-verified practice actions. 70 reported opens may include privacy prefetch; 8 new withdrawals. This data is provided, no real tracking performed. Use paper or a local document. Preserve the original case and make a separate changed-case record.
1. Step 1
Calculate delivery and unique-click measures separately.
You should see: Delivered 95; unique-click 12/95≈12.63%, not 20/95 as unique.
Keep the stated identifier, unit and policy alongside this result so another reader can check it.
2. Step 2
Label human-verified action measure and uncertainty.
You should see: 9/95≈9.47%; 3 uncertain click IDs not verified human.
Keep the stated identifier, unit and policy alongside this result so another reader can check it.
3. Step 3
Keep opens/withdrawals and privacy limitations visible.
You should see: 70 reported opens not 70 proved readers; 8 withdrawals must update ledger.
Keep the stated identifier, unit and policy alongside this result so another reader can check it.
4. Step 4
Save permission/segments/copy/QA/calendar/metrics campaign packet.
You should see: Fictional unsent plan with honest tracking limits; no claim of guaranteed sales, grant funding or email setup.
Keep the stated identifier, unit and policy alongside this result so another reader can check it.
What to finish
Save permission/segments/copy/QA/calendar/metrics campaign packet; include the original-case decision evidence and a separate changed-case result.
Watch for this
Turning automated tracking or repeated events into unique human engagement, learning or sales evidence.
How can I tell I understand it?
Using the supplied identifiers, I can save permission/segments/copy/QA/calendar/metrics campaign packet. My changed-case record names the revised condition and explains which dependent decision it changes.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-10-01
Public agency or educational context; no source exercises are copied and no simulated threshold is presented as an official rule. Page title and relevant content inspected; no interactive controls or credential process tested.
Access: Readable official page retrieved with the web reader on 2026-10-01.
Reuse: All teaching cases, data, worked steps and questions are original. Link and limited paraphrase for context; no copied source exercises.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.