Program and Campaign Architecture
Core Concepts
Programs are the building blocks of marketing activities in Marketo. Architects must design a program hierarchy (e.g., channel, folder structure) that supports reporting, reuse, and scalability. Key concepts: channels (define program types like Email, Webinar, Event), tags (for reporting), period costs, program statuses, and smart campaigns within programs. You must understand how to use program templates, local assets vs. global assets, and tokens for personalization. Also, engagement programs (nurture) and event programs have specific architectures.
Common Traps
- Inconsistent channel usage: Using the wrong channel or not defining statuses leads to broken reporting. Questions may ask about the impact of incorrect channel setup.
- Over-nesting folders: Deep folder structures complicate navigation and reporting; use a flat structure with tags.
- Not leveraging program templates: Templates ensure consistency and speed; architects should create templates for common program types.
- Ignoring program status progression: Smart campaigns must update program status to track success; missing this breaks attribution.
Worked Example
A company runs monthly webinars. Trap: creating each webinar as a separate program without a template. Better: create a webinar channel with statuses (Invited, Registered, Attended, No Show) and a program template with pre-built smart campaigns for registration, reminder, and follow-up. Use tokens for webinar-specific details. Rule of thumb: If you run the same type of program more than twice, templatize it.
Rule of Thumb
Design channels and statuses to reflect the customer journey; use tags for reporting dimensions (region, product).