personalization-logic

gtmagents's avatarfrom gtmagents

Use when defining dynamic content rules, tokens, and conditional offers inside nurture programs.

⭐31stars🔀7forks📁View on GitHub🕐Updated Dec 23, 2025
[CRM Workflows]

When & Why to Use This Skill

The Personalization Logic skill is designed to architect sophisticated dynamic content rules and conditional offers within marketing nurture programs. It provides a structured framework for mapping personalization tokens—such as industry, persona, and lifecycle stage—to specific content modules, ensuring highly relevant and automated messaging across email, in-app experiences, and digital advertising.

Use Cases

  • Lifecycle Marketing Automation: Designing complex branching logic for nurture sequences that adapt based on user behavior and product usage data.
  • Multi-Channel Personalization: Coordinating consistent messaging tokens across disparate platforms including CRM systems, ad networks, and SDR outreach tools.
  • Dynamic Content Strategy: Creating a modular content matrix that allows marketing operations to update proof points and CTAs without re-coding entire campaigns.
  • Data Governance & QA: Establishing token dictionaries and fallback rules to ensure brand consistency and prevent broken personalization in automated communications.
namepersonalization-logic
descriptionUse when defining dynamic content rules, tokens, and conditional offers

Nurture Personalization Logic Skill

When to Use

  • Building dynamic content for lifecycle nurtures.
  • Mapping personalization tokens (industry, role, behavior) to copy blocks.
  • Coordinating personalization across email, in-app, ads, and SDR assists.

Framework

  1. Segmentation Inputs – persona, industry, product usage, lifecycle stage, engagement history.
  2. Content Blocks – hero, proof, CTA, offer modules with variants per segment.
  3. Token Management – define data sources, fallback values, formatting rules.
  4. Testing Plan – structure A/B/C tests for personalization depth.
  5. Governance – approval workflows, localization, compliance, expirations.

Templates

  • Personalization matrix (segment vs module vs asset).
  • Token dictionary (field, source, fallback, formatting).
  • QA checklist (seed records, fallback coverage, compliance notes).

Tips

  • Start with modular blocks so ops can update without rewriting entire emails.
  • Document dependencies on upstream data hygiene.
  • Pair with copywriting + design teams for brand consistency.