strategist-catalog-strategy

Design catalog-driven personalization strategies using CSV or API imports, Liquid templates, and catalog triggers.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/delta-and-beta/braze-agency --skill strategist-catalog-strategy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strategist-catalog-strategy
Source: https://github.com/delta-and-beta/braze-agency/tree/main/skills/strategist-catalog-strategy
Command: npx skills add https://github.com/delta-and-beta/braze-agency --skill strategist-catalog-strategy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Designs and documents catalog-driven personalization approaches so teams can deliver dynamic, individually relevant product and event content without proliferating template variants or bloating user profiles. It clarifies how to structure catalog schemas, connect join keys to user attributes, and use Liquid, selections, triggers, and product blocks to keep templates stable while content varies per recipient.

Core Features & Use Cases

  • Catalog schema & import guidance: Recommendations for id fields, display fields, booleans, and CSV/API import constraints to make catalogs messaging-ready.
  • Selections + Liquid integration: Patterns for named selections and Liquid lookups to return per-user item sets and render them in messages.
  • Catalog triggers & workflows: Design patterns for back-in-stock, price-drop, and event-driven Canvas sends that react to catalog data changes.
  • Product blocks & rendering: Visual card-style rendering guidance for consistent multi-item displays across channels.
  • Use cases: Personalized product recommendation emails (top-N in-stock by category), back-in-stock notification flows for wishlisted items, and promotional flash sale alerts surfaced via catalog fields.

Quick Start

Design a catalog-driven email campaign that recommends three in-stock products per user using a named selection, Liquid rendering, and product blocks.

Frequently Asked Questions about strategist-catalog-strategy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I personalize email campaigns with catalog data at scale?

Catalog-driven personalization connects catalog schemas to user attributes via join keys, allowing Liquid templates and named selections to render dynamic product content per recipient without creating template variants.

How do I set up back-in-stock notification flows using catalog triggers?

Set up back-in-stock notification flows by configuring catalog triggers within Canvas workflows to react to catalog data changes. This event-driven approach surfaces updates to wishlisted items automatically across email, push, and in-app messaging channels.

What is the best way to structure catalog schemas for messaging readiness?

Structure catalog schemas for messaging by defining clear id fields, display fields, and booleans, while respecting CSV and API import constraints. Proper schema design ensures Liquid lookups and product blocks render correctly per user.

Can I use Liquid and product blocks to render dynamic product recommendations?

Yes, you can use Liquid templates with named selections to fetch per-user item sets and render them using product blocks. This visual card-style rendering ensures consistent multi-item displays across email, push, and in-app messaging channels.

Do I need to map join keys to user attributes for catalog selections to work?

Yes, mapping join keys to user attributes is required for catalog selections to return relevant per-user item sets. This connection allows named selections to filter catalog data and render personalized content dynamically within campaigns.

What are the limitations of using CSV imports for catalog-driven personalization?

CSV imports for catalog-driven personalization are limited by file formatting constraints and update frequency compared to API imports. Both methods require properly structured schemas with defined id and display fields to ensure messaging readiness across campaign workflows.