LearnGrokUse one matrix to turn approved messaging into distinct paid ad variants that can be checked and signed off. This is for performance marketers and campaign managers who need reviewers to approve copy without reconstructing the brief from scattered documents. You will finish with a set of copy rows, an evidence trail, and a clear recommendation for each row.
1. Assemble one approved input pack
Do not start by asking for ad ideas. Start by making the source material small, explicit and ordered. This prevents the model from treating a draft comment, a competitor claim or an old landing page as approved messaging.
Create a document called Campaign copy input pack with these sections:
- Campaign objective: the action the campaign is meant to drive and the measure your team will use.
- Approved positioning: the customer problem, product value, differentiator and brand language already agreed.
- Permitted claims: each claim, its proof point, and the source document or page where it was approved.
- Prohibited wording: claims, comparisons, promises, tone choices and phrases that must not appear.
- Landing-page message: the offer, page headline, proof, form or destination action. Paste the relevant page copy, not just its URL.
- Audience notes: the campaign-defined segment, its known job or use case, and any exclusions. Do not ask the model to infer personal traits.
- Placement rules: the exact fields you need, the character constraints from your active ad setup, approved calls to action, and the number of variants required.
Key point
Put approval before variation
The model can create different angles only from claims and language that have already been approved.
Keep the input pack as the working record for this round of copy. If an approver changes the value proposition, update the pack first. Do not fix individual rows by hand and leave the source unchanged.
Stop
Keep customer data out of the prompt
Do not paste customer lists, email addresses, account notes, conversion exports or other personal data. Audience notes should describe the campaign segment, not identifiable people.
2. Define what makes variants genuinely different
A matrix is not twelve rewrites of the same line. Give each variant one message angle. The angle changes the reason to act, while the approved positioning and offer stay fixed.
Choose angles that your input pack can support. Common choices include:
- The customer problem or friction being removed.
- A specific job to be done.
- A proven outcome, where the approved evidence supports it.
- A differentiator against the current way of working.
- An offer or next step, if the landing page makes that offer clear.
Do not use a competitor’s wording as a proposed claim. A competitor scan can help you identify market patterns, but it is not evidence for your campaign. Keep competitor observations in a separate note, labelled as observations, and bring only approved counter-positioning into the input pack.
Make a short angle plan before generating copy:
| Variant group | Angle | Approved support | Audience note |
|---|---|---|---|
| A | Remove a known workflow problem | Positioning statement 1 | Teams using the current manual process |
| B | Show the product differentiator | Approved feature and proof point | Buyers comparing established options |
| C | Lead with the offer | Landing-page offer section | Returning site visitors, where permitted in your plan |
If two rows use the same support and audience note, they need a different angle or they are duplicates.
3. Generate the matrix in one controlled request
Paste the input pack and angle plan into the model you are using. Ask for a table, not a narrative. This makes omissions visible and gives reviewers one place to work.
Use this request, replacing the bracketed text:
Create [number] paid ad variants from the approved input pack below.
Rules:
- Use only the approved claims, proof points, offer and calls to action.
- Do not invent statistics, customer results, comparisons, deadlines, availability, features or prices.
- Give each row one distinct message angle from the angle plan.
- Keep the headline, primary copy and CTA aligned with the landing-page message.
- Use the placement constraints exactly as supplied.
- Write audience notes as campaign segments or use cases. Do not infer sensitive or personal traits.
- Where a claim is used, name its source label from the input pack.
- Mark any missing evidence as `HOLD: evidence needed`, rather than filling the gap.
Return a Markdown table with these columns:
ID | message angle | headline | primary copy | CTA | audience note | claim source | sign-off recommendation | reviewer note
Set sign-off recommendation to one of: APPROVE, REVISE, or HOLD.
After the table, list: repeated angles, unsupported claims, landing-page mismatches, and assumptions that need approval.
[Paste Campaign copy input pack]
[Paste angle plan]
Check any version-dependent product controls or output behaviour against the xAI documentation overview before making this prompt part of a repeatable team process.
Watch out
Do not treat fluent copy as supported copy
A polished line can still add an unapproved promise. The claim source column is there to expose that problem.
4. Review the output row by row
Review the matrix against the input pack, not against whether you personally like the wording. Start with the evidence and destination, then review style.
For every row, check these fields in order:
- Message angle: it is meaningfully different from other rows.
- Headline and primary copy: each makes a claim found in the approved source named in
claim source. - CTA: it is on the approved CTA list and matches the destination action.
- Audience note: it matches the media plan and does not introduce an inferred characteristic.
- Landing-page fit: a click delivers the offer, proof and next step suggested by the ad.
- Sign-off recommendation: it reflects the checks above, rather than the model's confidence.
Check
A row is ready only when you can point to its source
If you cannot identify the approved wording, proof point or landing-page section behind a line, change the recommendation to HOLD or REVISE.
Use this triage table during review:
| If you see this | Recommendation | What to do |
|---|---|---|
| Copy uses an approved claim and matches the destination | APPROVE | Send it for normal brand and campaign approval. |
| The angle works but the wording is vague, repetitive or mismatched | REVISE | Edit the row, then repeat the row-level checks. |
| A claim, proof point, offer detail or deadline has no approved source | HOLD | Remove it or get the source material approved before regenerating. |
| Several rows differ only in adjectives or word order | REVISE | Replace duplicates with a new angle from the angle plan. |
5. Make the sign-off recommendation useful
Add an overall recommendation above the matrix when you circulate it. Keep it factual and short:
Approve 6 rows. Revise 3 for landing-page alignment. Hold 2 pending proof approval.No rows ready for sign-off. The input pack does not define permitted proof for the outcome claim.
Include the input-pack version or approval date used by your team, the landing page reviewed, and the reviewer responsible for each held item. This lets someone trace a row back to its source without reopening a long chat.
Copy the approved rows into the active ad build only after the final reviewer has signed off. Preserve the matrix as the record of what was approved and why.
When the matrix does not work
Do not restart with a broader request. Find the failed field first. If the variants sound alike, tighten the angle plan. If claims appear from nowhere, shorten the permitted-claims section and require a source label for every claim. If ads do not match the landing page, paste the relevant page section again and instruct the model to use its language.
Regenerate only the failed rows, with the existing approved rows kept as reference. That keeps the review set stable and turns the matrix into a working campaign habit rather than a one-off copy exercise.
