Magnum Systems — Giving an inherited Pardot instance a permission structure that holds up | Engage Evolution Skip to content
Engage Evolution
← Case studies
Magnum Systems Manufacturing Pardot / Marketing Cloud Account Engagement

Giving an inherited Pardot instance a permission structure that holds up

Rebuilt consent architecture, template system, and operating documentation for a Pardot instance inherited through an acquisition.

  • Pardot / MCAE architecture
  • Permission and consent design
  • Email template system
  • Operator documentation and SOPs

The situation

Magnum Systems runs Pardot alongside Salesforce, with contacts arriving from several directions — their own CRM, an acquired business unit, and a manufacturing platform that was never going to be integrated. The person responsible for the Pardot back end had inherited the configuration rather than built it, which is a common and underrated problem: you can operate a system day to day without having the model in your head, right up until something needs changing.

The pieces that needed attention were consent, templates, and the absence of anything written down.

What we did

Permission architecture. We designed a consent structure that could be explained and defended, covering how contacts from different sources enter the database, what each source implies about permission to mail, and how an invitation campaign could re-establish consent where provenance was unclear. The recommendation involved changing a long-standing auto-opt-in behavior, which took a conversation with leadership rather than a configuration change.

Email template system. A master template build with documented design tokens, plus a thank-you landing page, built so the internal team could produce sends without reopening the HTML each time.

Operating documentation. This is the part that outlives the engagement. A monthly batch import standard operating procedure for the recurring contact load coming out of the acquired unit’s platform, a list inventory so the instance’s structure is visible on one page, a website form integration specification for the site rebuild in progress, and a user guide for the email templates — written as step-by-step instructions for the person who has to run it, not as reference material.

Where it landed

The instance now has a consent model somebody can articulate, a template system that does not require a developer for routine sends, and documentation that means the next person to inherit it will not be starting where we started.

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