Troubleshoot content issues
Content issues fall into two groups. Creative issues are about how a message looks or sounds, and most come from what's in Marketing agent's memory. Personalization issues are about dynamic content that doesn't resolve, and most come from data that doesn't match what personalization expects.
Creative issues
When the design or wording isn't what you expect, check memory first: Marketing agent follows what's saved there, including your brand kit.
| What you see | What to do |
|---|---|
| It doesn't use your headers | Check that your headers are in memory, with a rule for when to use each. |
| It keeps changing the models in pictures | Add an image rule to memory. See Generate images. |
| It keeps using the wrong terminology | Check memory for outdated or conflicting terms, and add the terms you want. |
| It repeats the same blocks over and over | Add more block examples to memory, or ask Marketing agent to create some new designs. |
| It uses the template you asked for, but the colors aren't right | Check memory for conflicting instructions, such as brand colors that differ from the template's. |
Personalization issues
When dynamic content is empty, wrong, or stops the message, ask Marketing agent to find the cause and propose a fix. For what each error means, see Preview and test.
Fix it with Marketing agent
- Read the message in preview. It usually says what's missing.
- Ask Marketing agent to find the cause and propose fixes.
- Approve the fix and preview again.
Why is this product block aborting for this customer? Find the cause and suggest a fix.Common personalization issues
| What you see | Likely cause | What to do |
|---|---|---|
| Abort message in preview | Data or a personalization value is missing for that customer, so Marketing agent stopped the message. | Read the message, then ask Marketing agent to explain the block and fix the cause. |
| Personalization code error | The personalization code fails on an edge case. | Ask Marketing agent to find the cause and propose a fix. |
| Placeholder instead of a real voucher code | The code is drawn from a voucher pool in the scenario, which happens only when the scenario runs. | Preview can't show a pool code without running the scenario, so it shows the fallback. Change the fallback to a representative value to check that it reads well, or ask Marketing agent to use a customer attribute that stores the voucher instead. |
| Wrong products | The aggregate or recommendation logic doesn't select the products you want. | Open the aggregate or recommendation artifact to check its logic, such as its filters. Ask Marketing agent to change it. |
Updated about 1 hour ago
Did this page help you?

