Marketo
Three silent send failures on Marketo.
Marketo Smart Campaigns sit on top of lead activity, list membership, and Smart Lists, and most silent failures are upstream changes that the Smart Campaign accepts as a normal state. Three silent stops the community reports most often on Marketo.
The detection gap
What changes when a flow is instrumented.
A silent send failure follows the same six steps on every ESP. The platform handles the first two well. The next four are where the lag lives, and where the wallet card flips the timeline.
Step
Your ESP today
With Telltide instrumented
1. Trigger fires
Logged
Identical, the ESP handles this
2. Send leaves platform
Counted
Identical, the ESP handles this
3. Send fails silently
No surface
Wallet card flips amber
4. You are alerted
Not until a customer complains
Lock-screen banner within minutes
5. Triage starts
Hours later, on the next dashboard scan
From the wallet card, on the same screen
6. Fix lands
After revenue impact is visible
Before revenue impact is visible
The lag is not a tooling absence. It is the difference between a per-event log and a status surface a human checks without thinking. The wallet card is that surface.
Pattern 1 of 3
Smart Campaign trigger relies on a lead activity that was renamed
What it looks like
A trigger waits on a custom activity such as Visited Booth or Watched Webinar. The activity is renamed during an event refresh. The trigger now waits on an activity that no longer fires. The Smart Campaign is Active and waiting.
Why detection lags
Marketo treats a waiting trigger as healthy. There is no surfaced signal that the activity has dried up. The drop is visible only in the trigger event count and only if someone is watching.
Marketo treats a waiting trigger as healthy.
Telltide alert email, illustrative
Subject: Monitor missed: Webinar follow-up
MISSED WINDOW
No email received: Webinar follow-up
The Day-1 follow-up window closed without a matching email.
Investigate monitor →
What to instrument
Seed leads that fire the trigger activity validate the campaign. If seeds get through, the live trigger is intact; if seeds stop, the activity has been renamed.
Pattern 2 of 3
A/B test variant has zero audience after a Smart List change
What it looks like
An Email Program's A/B test variant is constrained by a Smart List filter. A Smart List rewrite changes the filter logic. The variant now matches zero leads. The other variants absorb the audience and the test reports running.
Why detection lags
Marketo accepts zero-audience variants as a configuration choice. There is no warning. The test reads as healthy in aggregate.
There is no warning when a variant matches zero leads.
What to instrument
Seed leads matching the variant's intended audience validate the variant. If the seed lands one variant only, the others are silently dead.
Pattern 3 of 3
Sales Insight or integration token expiry breaks the enrol step
What it looks like
A campaign's enrol step depends on an integration that uses a refresh token. The token expires or is revoked. New enrollments stop reaching the integration. The Smart Campaign keeps reporting Active.
Why detection lags
Marketo logs integration errors per call, but the Smart Campaign-level status does not reflect them. Sales notices the gap after a week of stale lead routing.
Integration errors do not roll up to the Smart Campaign status.
What to instrument
Seed leads driven through the same enrol step land the downstream message or do not. A silent seed flag means the integration token is the failure, not the campaign logic.
Self-audit
Ten ticks. Each one you cannot mark is exposure.
Run this against your own programme. If you finish with three or more unticked, the case for instrumenting one flow this week is the rest of this document.
-
Trigger metrics for your top three flows are reviewed monthly for rename and event-shape drift.
-
Send-skip reasons (send-time optimisation, frequency caps, send classifications, suppression hits) are aggregated to a per-flow report you maintain, since the platform does not roll them up.
-
Webhooks the flow depends on, inbound triggers and outbound callouts both, are pinged on a separate health check that fires independently of the flow.
-
Catalogue or product feed fields used in flow filters have a daily canary record that matches the filter clause and fails the build if the match returns zero.
-
Audience filters on each live flow alert if the matching profile count drops by more than a configured share week-over-week.
-
A pre-send validator catches broken template syntax and unresolved merge tags on every send, not only the compose-time linter.
-
Suppression lists driven by upstream integrations are monitored for runaway growth above a daily baseline.
-
Subscription type, consent, or preference centre changes are versioned and diffed against the previous published state before publish, so silent removals are caught.
-
Lists, segments, or upstream data feeds that power live flows have a freshness SLA and an alert if the SLA breaks.
-
Every flow critical to revenue has a seed address subscribed to it that lands within the flow's normal arrival window.
Detection Guarantee
The Detection Guarantee covers your first 90 days on Starter. If we miss a silent send failure on a monitored flow inside that window, we credit up to three months of the affected tier. One page of terms, plain English, no carve-outs.
2:12
Detail
Welcome 1 missed window
Updated
18 May 2026, 2:12 pm
Your Telltide Card. Green when every monitor is healthy. Flips amber and pushes to your lock screen the moment a flow stops sending.
Start free, instrument one flow. The wallet card unlocks on Starter, with a fourteen-day free trial when you add it. Roughly ten minutes end to end.
Marketo