Who to reach and how the account is built · 30 min
Pixel + CAPI: PageView, Lead, Schedule
In this lesson
- Say which events to fire, which to use for optimization, and which never to invent
Three events. Two jobs. Zero fiction.
PageView fires on every page load. It fills the retargeting pool and proves the pixel is alive. It is not a conversion you optimize toward on a $3,000 lead account. Lead fires when a form is submitted — Instant Form or site form. If that form is only name + phone, Meta will hunt the cheapest curiosity in Frederick. Schedule fires when a lot visit is actually booked (calendar confirm or CRM status the desk trusts). That is the event you want to optimize toward. ViewContent on a VDP is useful for retargeting a CR-V shopper; it is not the win condition. Purchase is for money that changed hands. Do not fire Purchase at the average asking price every time someone asks for a Saturday slot.
CAPI is a second copy, not a second truth
The Conversions API (CAPI) sends the same events from your server or CRM with an event_id so Meta can deduplicate the browser pixel. Instrument CAPI when you have a webhook or CRM confirm — especially Schedule, because ad blockers miss a lot of browser Lead events. Do not invent CAPI if there is no server path. Do not fire a CRM “note added” as Lead. Do not send a custom HotBuyer event you cannot define in one sentence. If Dana’s site has no developer this month, say: browser PageView + browser Lead on the thank-you page, Schedule queued until the CRM can post it. Label the gap. Do not draw a finished CAPI diagram you cannot build.
Never invent Purchase value, ROAS, or a custom event count so the board looks complete. If Schedule is not wired, write “not instrumented — optimize to qualified Lead until it is.”
Exercise
Event instrumentation card
For PageView, ViewContent, Lead, Schedule, and Purchase: fire? (yes/no/later), where (browser / CAPI / both / nowhere), optimize toward? (yes/no), one-line reason. Assume Dana has a thank-you page and no CAPI yet.
Deliverable: A 5-row event card: event, fire, where, optimize, why.
Create a free account and verify your email to save progress, quizzes, and portfolio work. Create a free Academy account · Sign in
Audience and structure check
Assignment
Audience + campaign structure board
Build a table a second buyer could open in Ads Manager: campaign name, objective, CBO or ABO, monthly budget, ad set name, audience stance (broad / one-interest probe / retargeting window / exclusions), optimization event (PageView / Lead / Schedule — and whether it is wired), placement note. Use Northfield’s $3,000/month. Include the 6-row targeting stance table and the 5-row event card. Prospecting and retargeting must not share a CBO. Do not invent CPM, ROAS, or Purchase value.
Deliverable: Structure table + 6-row targeting stance + 5-row event card. One sentence defending the retargeting cap.
Write at least a short brief (80+ characters). A mentor reviews for a pass.
Ask the tutor
The tutor will guide you. It will not finish graded work for you.
