The Prompt
You are a senior demand gen operator with deep Marketo expertise, diagnosing why a specific paid-sourced lead did not enter the expected nurture program. You understand that B2B paid budget is wasted when leads generated by ads fail to receive nurture — and that the reasons are rarely visible without a record-by-record audit.
INPUTS
I will paste a Marketo activity log export below — typically pulled as XLS from the Marketo activity log view for an individual lead record. The export should include: lifecycle status history, email send and opt-out events, program membership changes (Add to Flow / Remove from Flow), Master Marketo Send List membership changes, SFDC CRM sync events, and country / geo / subregion field values.
{PASTE_MARKETO_ACTIVITY_LOG_HERE}
{OPTIONAL_PASTE_LEAD_CONTEXT_HERE}
(Examples: "Lead came from LinkedIn campaign X on date Y," "Sales flagged this lead as not receiving follow-up." Leave blank if no context to add.)
WHAT I NEED FROM YOU
Diagnose why this lead did not enter the expected nurture program. Produce the output in this exact order:
1. Timeline Reconstruction
A chronological list of every event in the activity log that affects nurture eligibility:
- Form fill / lead created
- Lifecycle status changes (MQL, SQL, DQ, Nurture flags) with timestamps
- Email send events and any opt-out / unsubscribe flags
- Program membership changes (Add to Flow, Remove from Flow)
- Master Marketo Send List membership changes
- SFDC CRM sync events that may have altered the record
- Country / subregion field changes
2. Root Cause Identification
Identify which specific gate blocked nurture entry. Match against the known blocker types:
- Master Marketo Send List exclusion: highest-risk black-box gate. The lead may be excluded from this list, blocking all email eligibility regardless of other criteria.
- Unsubscribe / Opt-out flag: legacy unsubscribe on record permanently blocks nurture sends until manually resolved.
- Lifecycle Status mismatch: lead is in the wrong lifecycle stage (e.g., previously SQL or DQ) and does not qualify under current net-new entry logic.
- Re-engagement window aging: older lead re-engaged via a new form fill but has aged out of the 60-day re-engagement eligibility window.
- EMEA segmentation gap: country / subregion field does not match the geo logic in the nurture program (especially common for UKI leads in NAMER-built programs).
- SFDC sync interference: CRM sync event after lead creation altered lifecycle status, account assignment, or other qualifying fields in a way that retroactively disqualified the record.
State the single primary cause. If multiple gates blocked entry, list them in order of which fired first.
3. Recommended Action
Specific action for MoPs or RevOps to resolve this case. Format: "Recommend: [action]. Owner: [MoPs / RevOps / Sales]. Expected resolution time: [days]."
4. Systemic Pattern Flag
Indicate whether this looks like a one-off issue or a likely pattern indicator. If pattern: recommend pulling a sample of N similar leads to confirm.
JUDGMENT RULES
- Match against the documented blocker types before reaching for novel explanations. 95%+ of cases match one of the six known gates.
- The Master Marketo Send List is the most common root cause and the hardest to diagnose without explicit data on list membership. If the activity log doesn't include Master Marketo Send List events, flag the diagnosis as incomplete and recommend pulling that data.
- Lifecycle status mismatches are common after SFDC sync. If a sync event appears in the timeline immediately before the missing nurture entry, that sync is the most likely cause.
- Re-engagement aging is silent — Marketo doesn't surface "this lead aged out" as an explicit event. If the lead's original form fill was more than 60 days before the recent activity, flag re-engagement aging as a candidate.
- If the activity log is incomplete or the relevant events are missing, say so explicitly. Do not invent timeline events. Be honest with me — fabricated diagnostics waste MoPs cycles on the wrong fix.
OUTPUT FORMAT
Return as {OUTPUT_FORMAT}.
If "markdown": structured diagnostic note with timeline, root cause, action, and pattern flag.
If "html": semantic HTML formatted as a per-record diagnostic that can be appended to a multi-record audit report.
Begin.
How to Use It
This prompt is built for MoPs and RevOps operators who need to diagnose individual lead routing failures without a 2-hour activity log review. The six blocker types it matches against come from real Q1 FY27 audit work — they're not theoretical categories. The Master Marketo Send List gate is the most important one to understand: it's a black-box exclusion list that overrides virtually every other nurture eligibility criterion, and it's the most common root cause that goes undiagnosed because it doesn't surface as an explicit "excluded" event in the activity log. Claude handles the timeline reconstruction and pattern-matching here significantly better than ChatGPT — Claude's structured reasoning about event sequencing and its willingness to say "this diagnosis is incomplete without the Master Marketo Send List data" is a material difference in production use.
The output flows in four steps: timeline reconstruction (every event in the activity log that affects nurture eligibility, in chronological order), root cause identification (matched against the six known blocker types), a recommended action (with a specific owner and expected resolution time), and a systemic pattern flag (whether this looks like a one-off or a symptom of a broader problem). That last output is the one that often drives the most value — a single-record diagnostic that also flags "this pattern appears in 15% of paid-sourced leads from EMEA in Q1" turns a ticket into a remediation project.
The input is a Marketo activity log export — typically pulled as XLS from the individual lead record view. Include lifecycle status history, email send and opt-out events, program membership changes, Master Marketo Send List membership changes, SFDC CRM sync events, and country/geo/subregion field values. The more complete the export, the more reliable the diagnosis. An optional context field accepts notes from Sales or BDR about why they flagged the lead — that context helps the model weight the timeline correctly.
Example Output
Lead: [REDACTED] — LinkedIn Doc Ad Q1 FY27 (UKI)
Timeline Reconstruction
- 2026-02-14: Form fill via LinkedIn Doc Ad campaign (UKI-targeted). Lead created in Marketo.
- 2026-02-14: Lifecycle Status → "New Lead" (correct net-new entry status)
- 2026-02-14: SFDC sync event 4 hours later — Country field updated from "GB" to "United Kingdom" (string format change)
- 2026-02-15: Expected Prospect Nurture — Net New entry — did NOT fire
- 2026-02-15 to 2026-04-01: No nurture emails sent
- 2026-04-01: Sales flagged record as "no follow-up received"
Root Cause Identification
Primary cause: EMEA segmentation gap.
The nurture program's entry logic filters on Country = "GB" (the exact string used in LinkedIn Lead Gen form output). When the SFDC sync rewrote the Country field to "United Kingdom" 4 hours after creation, the lead no longer matched the entry criteria. The program is NAMER-built with EMEA-as-afterthought logic, and the country string mismatch is a known failure pattern documented in the Q1 FY27 audit.
Recommended Action
Recommend: (1) Update the Prospect Nurture entry filter to accept multiple Country string formats for UK/UKI ("GB," "United Kingdom," "UK"). (2) Add this lead to the nurture program manually as a backfill. Owner: MoPs (filter update) + RevOps (sync rule review). Expected resolution time: 3-5 days for filter update; immediate for manual backfill.
Systemic Pattern Flag
Pattern indicator. This is the third UKI lead this quarter diagnosed with the same root cause. Recommend pulling a sample of 20 UKI LinkedIn leads from the last 90 days and auditing the Country field state at the time of expected nurture entry. If the pattern holds, this is a systemic gap affecting all UKI LinkedIn pipeline.
Illustrative example based on the documented EMEA segmentation gap from the Q1 FY27 audit. Will be replaced with a redacted live diagnostic from an upcoming Marketo audit cycle.
Common Failure Modes
- Inventing timeline events that aren't in the activity log. First version constructed a clean narrative even when the Marketo export was missing key events. The "do not invent timeline events" rule is the fix — if the Master Marketo Send List events aren't in the export, the model now flags the diagnosis as incomplete instead of guessing.
- Reaching for novel explanations before checking the six known blockers. Early outputs would propose "the email template may have failed validation" or "there could be a Marketo API rate limit issue" before checking against the documented blocker types. 95%+ of real cases match one of the six gates from the Q1 FY27 audit. The judgment rule forces the model to match against known patterns first.
- Missing the silent re-engagement aging gate. Re-engagement aging is the hardest blocker to spot because Marketo doesn't fire an explicit "aged out" event. If the original form fill was more than 60 days before the recent activity, the lead may be silently disqualified from the 60-day re-engagement track. The model misses this unless you remind it to check the original lead creation date against the 60-day window — which is now baked into the judgment rules.
Variations
Two variations of this prompt are worth knowing.
Variation 1: Bulk Audit Version
Adapted for auditing a batch of 10–20 lead records from a single campaign in parallel, rather than a single record. Surfaces pattern-level findings across the batch — useful for post-campaign MoPs reviews when you need to confirm nurture enrollment rates rather than diagnose individual failures.
[PROMPT GOES HERE]
Variation 2: EMEA Segmentation Audit Version
Focused specifically on the EMEA segmentation gap blocker — diagnosing leads where the country/subregion field doesn't match the geo logic in NAMER-built nurture programs. A common pattern for UKI leads enrolled in North America program logic.
[PROMPT GOES HERE]
Get one new prompt every Monday.
Plus the system behind it. Free. Built for in-house demand gen managers at B2B SaaS companies.
Subscribe free →Frequently Asked Questions
What data do I need from Marketo to run this diagnostic?
A Marketo activity log export for the individual lead record — typically pulled as XLS from the activity log view. Required fields: lifecycle status history with timestamps, email send events and opt-out/unsubscribe events, program membership changes (Add to Flow, Remove from Flow), Master Marketo Send List membership changes, SFDC CRM sync events, and country/geo/subregion field values. If the Master Marketo Send List events aren't in the export, the prompt will flag the diagnosis as incomplete — that's the most important field to include.
Why is the Master Marketo Send List the highest-risk black-box gate?
Because exclusion from the Master Marketo Send List blocks all email eligibility across the entire instance — it overrides program-level enrollment, lifecycle status, and re-engagement logic simultaneously. A lead can be perfectly configured for nurture on every other dimension and still receive zero emails if this list excludes them. And unlike an unsubscribe flag (which appears as an explicit event), Master Marketo Send List exclusion is often invisible in the standard activity view, requiring a specific data pull to confirm. That combination — high impact, low visibility — makes it the most dangerous and most-missed blocker.
How is this different from a standard Marketo audit?
A standard Marketo audit reviews program-level configuration — enrollment criteria, flow steps, send limits. This prompt diagnoses individual record failures against record-level data. The distinction matters because program configuration can be correct and individual records can still fail to enroll due to record-specific states (a legacy unsubscribe flag from 3 years ago, an SFDC sync event that arrived 4 minutes after form fill and changed lifecycle status). Program audits won't find those. Record-level diagnostics will.
What does the systemic pattern flag output mean in practice?
It's the prompt's way of telling you whether this individual failure is likely a symptom of a broader problem. If the diagnosis is "lifecycle status mismatch due to SFDC sync interference" and that pattern appears repeatedly across similar records, the right response isn't to fix the individual record — it's to fix the sync rule causing the mismatch. The systemic pattern flag recommends a sample size to pull ("pull 20 similar EMEA leads from Campaign X and check for the same SFDC sync timing") so you can confirm whether to escalate from a ticket to a remediation project.