Core concepts

This page introduces the key concepts Marketing agent is built around: the brief, memory, and artifacts.

Brief

The brief is the structured summary the agent builds from your prompt — audience, content, timing, and goal — before the agent builds the actual campaign. It's the agent's plan, not the finished campaign.

Review, adjust, and approve the brief before the campaign is built. See how to review the brief to read and adjust one, or how the agent makes decisions to learn what shapes the brief.

Memory

The agent remembers details you share about your business, brand, and you, and applies them automatically — across every conversation, not just the one where you said it.

Tell the agent your business never uses vouchers, or that wait times should always be at least 24 hours, and the agent carries that rule going forward without you repeating it.

Memory splits into:

• Organization memory: Grouped into categories like brand identity, voice and copy rules, visual design, campaign operations, CRM strategy, and legal and compliance.
• User memory: Details about you specifically.

Review, edit, or delete anything the agent has remembered from the Memory page. Read the prompt guidelines to learn how the agent applies remembered rules as you build, or how the agent uses AI to learn how memory fits into its wider data handling.

Artifacts

The agent tracks two kinds of artifacts: your campaign itself, and the supporting aggregates it builds along the way — for example, a purchase-history filter or a browse-behavior count that powers a recommendation or a personalized product grid. Each one gets a stable identity, a draft history you can review, and a durable link to the live version once it's published to Marketing.

Nothing reaches Marketing until you approve it. The agent drafts an artifact, validates it against your project data, and only publishes it on your approval. The agent then creates or updates the Marketing resource.

Reuse artifacts

Artifacts can also reference each other. If your campaign needs an audience split that already exists as an artifact, the agent reuses it instead of rebuilding it from scratch. A new dependency the agent creates to support your campaign is saved automatically, but your own campaign is never saved without your approval.