Rebuilding patient and HCP journeys for a pharma brand
Rebuilt patient and healthcare-professional journeys across multiple versions for a pharma agency, delivered as a named subcontractor at fixed fees.
- Journey Builder rebuilds and versioning
- Data extension backup automation
- Resend and echo logic
- White-label agency delivery
The situation
BNO is an agency running Marketing Cloud for a pharmaceutical brand, with separate journeys for patients and for healthcare professionals. Journeys had accumulated versions — patient and HCP journeys each several iterations deep, plus catch-up journeys for contacts who had already completed an earlier version. Keeping track of which contacts should land in which version of which journey had become the hard part.
They needed a Marketing Cloud specialist on the build, not a new agency.
What we did
Journey rebuild and version control. We revised the patient and HCP journeys to add new emails and contact-update steps across multiple paths, made sure contacts entered the correct journey version, stopped the superseded running versions, and confirmed that contacts who had already completed an earlier journey but met the new criteria still received the new email.
Two faults came out of that work. A decision split was routing on a stale eligibility flag. And 73 records were being wrongly excluded from the HCP journey by a mismatched field value — the kind of thing that never shows up in a report, because the records simply are not there.
Resend logic across a 28-email set. We implemented echo sends: if a recipient had not opened within a week, the same email went again with a new subject line and preheader.
Before building it, we flagged that open rates stopped being a reliable signal after Apple Mail Privacy Protection — any provider using it anonymizes the data and reports the recipient as a non-opener. We recommended evaluating on opens and clicks instead, and advised against resending the same email more than once. The client made the call with that in front of them, which is the point.
Data extension backup. A scheduled automation copying data extensions to the client’s external FTP on a set cadence. We noted at the time that an in-platform archive would be the better long-term pattern, and said so rather than just building the thing that was asked for.
How we worked
Delivered as a named subcontractor, at a fixed fee per deliverable with assumptions and exclusions written into each line item. HTML and CSS production, design, copywriting, custom reporting and render testing were excluded by default, so the agency could price and mark up the work with confidence.
Something similar on your side?
Thirty minutes, no deck. Tell me what's going on and I'll give you a straight read on it.
Book a working session