◆ Mailchimp

Insert dynamic merge tags

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskInsert dynamic merge tags into the welcome series to personalize subject lines and body copy.…+
Insert dynamic merge tags into the welcome series to personalize subject lines and body copy. Put FirstName in the subject using the fallback 'there' for missing names, include LastOrderItem in the first paragraph but show 'a recent purchase' if empty, and show the loyalty tier badge inline only for subscribers with Loyalty=Gold or Platinum. Test the three variants using sample subscribers who lack each of these fields and give me the raw send preview for approval by Wednesday.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I finalize merge tags, make it easy for the reviewer to approve: surface which fields…+
Before I finalize merge tags, make it easy for the reviewer to approve: surface which fields are missing most often, show how the subject line reads for subscribers missing FirstName, flag any tags that will expose backend codes instead of friendly names (like internal product IDs), and recommend fallbacks that sound natural. Pick one fallback per field to avoid inconsistent copy across the series.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentIn the welcome email preview, LastOrderItem showed an internal SKU instead of 'Monthly…+
I added merge tags and some previews look odd.
In the welcome email preview, LastOrderItem showed an internal SKU instead of 'Monthly Subscription' for several test accounts. I'm afraid merge tags will leak internal codes to real subscribers. Where is that mismatch coming from — mapping in the export, a field value problem, or the tag itself — and what is the quickest corrective step to ensure user-facing labels appear instead of SKUs?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross campaigns we've embarrassed a few customers by leaking internal codes or by showing raw…+
We keep sending emails with broken merge tag fallbacks or internal codes.
Across campaigns we've embarrassed a few customers by leaking internal codes or by showing raw fallbacks like 'there' inconsistently. Which habit is causing most errors — lack of canonical field values, poor previewing, or ad-hoc fallbacks — and what three practical changes will stop this: a canonical look-up table for display names, mandatory preview tests with empty-field samples, and a documented fallback style guide?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Mailchimp's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.