Skip to content
English
  • There are no suggestions because the search field is empty.

Utilizing Marketing Campaign Blueprints


Creating and Managing Campaign Blueprints

What is a Blueprint?
A Blueprint is a reusable campaign template that bundles:

  • Triggers: when to send (for example, inventory change, date/time, audience action)

  • Audience logic: who should receive it (segments and exclusions)

  • Message content: email/SMS content with dynamic tags

  • Settings: send domain, throttling, and frequency caps
    Use blueprints to standardize best-practice campaigns your team can launch quickly with minimal edits.

Before You Begin

  • Confirm you can access Promote → Campaigns.

  • Ensure at least one verified send domain is available.

  • Have brand assets and any required dynamic fields ready (for example, event name, URL, image).

Create a Blueprint

  1. Open Campaigns
    Go to Promote → Campaigns and click Create Campaign.

  2. Choose “Blueprints”
    Select Blueprints to start from a guided template rather than a blank canvas.

  3. Pick a Starting Pattern
    Browse common patterns, such as On-sale announcement, Low inventory nudge, Post-purchase add-on, Artist announce, or Reminder/Last call. Pick the closest match.

  4. Set the Trigger
    Choose the condition that starts the send, such as:

    • Date/Time: fixed schedule or relative to event date

    • Behavioral: viewed event, abandoned checkout, joined list

    • Status: inventory level, status change, price tier change
      Tip: Add safeguards (for example, minimum audience size) to avoid accidental sends.

  5. Define the Audience
    Include the segments you want and set exclusions (for example, exclude purchasers or recent recipients). Save the audience for reuse if needed.

  6. Build the Message
    Use the drag-and-drop editor to customize:

    • Subject/Preheader

    • Hero image and body copy

    • CTA buttons with the correct destination URL

    • Dynamic tags such as {EventName}, {EventImage}, {EventUrl}
      Note: Provide fallbacks for any tag that might be missing (for example, a placeholder image).

  7. Configure Settings

    • Send domain

    • Frequency caps and throttling

    • UTM tracking (optional)

  8. Test
    Send yourself a proof, check link tracking, and confirm tags resolve correctly.

  9. Save as Blueprint
    Choose Save as Blueprint (or Publish Template, depending on your UI). Add a clear name and description so teammates know when to use it.

Launch a Campaign From a Blueprint

  1. New Campaign → From Blueprint

  2. Select your saved blueprint and review trigger, audience, and content.

  3. Make any event-specific edits (dates, copy, images).

  4. Select your send domain and Start Campaign.

Best Practices

  • One objective per blueprint: keep the message and primary CTA focused.

  • Segment thoughtfully: include/exclude based on purchase status and recency.

  • Name clearly: examples — “Reminder — 24h before show (excludes buyers)” or “Post-purchase add-on — 2h after purchase.”

  • Version control: clone and iterate rather than overwriting a strong performer.

  • Test subject lines: short, specific, and action-oriented.

Troubleshooting

  • Blueprint doesn’t appear at launch: ensure it’s published, not just saved as a draft.

  • Dynamic tags show blanks: check the source fields and add fallbacks.

  • Audience is 0: loosen filters or verify the segment sync.

  • Domain missing: re-verify DNS and domain status in Settings.

FAQs

  • Can I edit a blueprint after publishing?
    Yes. Create a new version or clone it to preserve history.

  • Can I run a one-time send with a blueprint?
    Yes. Select the blueprint, remove the trigger, and schedule a single send.

  • Can I share blueprints across teams or venues?
    If your plan and permissions allow, you can share or export. Add a descriptive summary so others understand its use case.

Related

  • Campaigns overview and statuses (Active, Paused, Draft)

  • Audience segmentation and exclusions

  • Domain verification and deliverability

  • Dynamic tag reference