TrueTail Pet Insurance - Coverage Match Nurture Program

August 24, 2026 TrueTail Pet Insurance - Coverage Match Nurture Program

Marketing operations - automated journey design

TrueTail Pet Insurance: coverage-match nurture program

A single welcome email routes new pet parents into one of five species-specific nurture tracks based on first-party click behavior - no guessing, no generic follow-up. Built to demonstrate multi-program MCAE/Pardot architecture: page-action based segmentation, completion-action enrollment, action-rule suppression, and ad-hoc list overrides for manual sales requests.

Fictional brand - illustrative data only
Shown in full: Bird coverage
Shown condensed: Dog, Cat, Rabbit, Fish & aquatic (identical structure)
New pet parent enters welcome series
General "New Pet Parent" Salesforce campaign
Welcome email sent
Features the top article, video, and podcast for each of the five coverage types - one link per pet
design extension - not built
SMS sent same day
Third-party SMS platform, triggered via Salesforce Flow · invites a reply confirming pet name, type, age, sex, and location to sharpen content matching beyond click behavior alone
prospect clicks an email asset - OR - replies to the SMS - OR - visits a matching page directly (e.g. via social)
Page action / completion action fires
Adds prospect to the matching coverage list, now informed by declared profile data · action rule removes them from the general welcome campaign
Dog
coverage program
Cat
coverage program
Rabbit
coverage program
Fish
coverage program

Bird coverage program - shown in full

All five programs share this exact structure. Bird is drawn in detail here. The other four are identical in mechanism with species-specific content, shown condensed below.

Entry: "bird_coverage_page_action" tag added to profile
Fires on email click OR direct page visit
Added to Bird Coverage static enrollment list
Ad-hoc list - sales can manually add or exclude specific prospects regardless of behavior
Added to Bird Coverage Nurture Salesforce campaign
Email sent
Bird-specific coverage content
Wait 3 days
Link clicked?
yes
Added to Bird Coverage success list
Suppressed from further nurture
end - sales handoff
no
Continues to next email
repeats through emails 2-4, same send → wait → click check
end - unsuccessful list, tagged for 6-month re-engagement
Dog coverage
Identical 4-email nurture cycle, dog-specific content and completion lists
Cat coverage
Identical 4-email nurture cycle, cat-specific content and completion lists
Rabbit coverage
Identical 4-email nurture cycle, rabbit-specific content and completion lists
Fish & aquatic coverage
Identical 4-email nurture cycle, fish-specific content and completion lists

Results brief

Why this was built, and what happened

The architecture above recreates a real Salesforce Marketing Cloud Account Engagement program I built and owned. The results below reflect real reporting from that program, described as patterns and ranges rather than exact figures.

The problem

New prospects moving through TrueTail's general welcome series received identical messaging regardless of which pet they actually needed coverage for. There was no way to identify a species-specific interest until someone filled out a form, and most people never did.

The approach

  • Welcome email surfaced the best article, video, and podcast for all five coverage types at once, and a click became the routing signal
  • A page action captured the same signal from direct page visits, so social traffic routed identically to email clicks
  • An action rule removed a prospect from the general campaign the instant they entered a species-specific branch
  • Static ad-hoc lists let sales manually add or exclude specific prospects, independent of the automated logic

The result

  • Every branch total reconciled exactly against the program-wide totals across a full year of reporting
  • Branch-specific email engagement outperformed the general campaign by roughly 2x on average, with the strongest branch trending closer to 2.5x
  • Prospects who self-identified into a coverage-specific branch represented a small share of the overall population, well under 5 percent, consistent with an opt-in signal rather than a shortfall
  • The ad-hoc override mechanism saw real production use: leads and a closed opportunity appeared attributed to a branch with zero formal email enrollments

Design extension: SMS profile enrichment

not built

The SMS step above is a forward extension, not part of the original build. Validating it would mean tracking SMS opt-in rate, how often a reply's stated pet type matched the branch a prospect eventually clicked into, and whether branch-assignment accuracy improved for SMS responders compared to click-only routing.

noteEvery branch supports static ad-hoc lists layered on top of the behavioral logic. Sales can request a specific prospect be manually added to or excluded from any program at any time, independent of their click behavior.
noteEntering any coverage-specific program always triggers suppression from the general welcome campaign via an action rule, so no prospect receives both tracks simultaneously.