WhatsApp template rejected: example does not match variable format

If Meta rejected a WhatsApp template because the example doesn't match the variable format, it's not serious and you can almost always fix it yourself. It means the sample text you entered to replace the variable doesn't follow the format Meta expects for that type of data. It's not a problem with your account, nor a penalty, nor something that blocks your number: it's an observation about how you wrote the example, and it's fixed by editing the template and resubmitting it for review.

The most common confusion is believing the problem is in the fixed text of the template, when it's actually in the example: that sample value Meta uses to understand what will go in the variable's placeholder. If that example has a format it doesn't accept, it rejects the entire template even if the rest is perfect.

What exactly "the example doesn't match the variable format" means

When you build a template with variables, each placeholder carries two things: the variable itself (for example {{1}}) and a sample value that tells Meta what type of content goes there. That example isn't decorative: it's the reference the system uses to validate that the template is clear and that the replacement makes sense.

The rejection appears when that example doesn't follow the expected format for the variable type. Simply put: you wrote an example that Meta can't read as the type of data you declared. The template itself may be well written, but the example makes it fail.

Why it appears: the most frequent causes

The error almost always comes from one of these four situations. Review them in order: most rejections for this reason fall into the first or second.

• The example has a format that does not match the variable type. For example, you declared a variable of type number or date and in the example you wrote free text, or the other way around.
• The example is empty or generic. You left the example blank, put "..." or wrote something like "sample text" that does not represent the real data that will go there.
• The example includes characters that Meta does not expect in that slot: quotation marks, line breaks, unusual emojis or signs that break the reading of the replacement.
• The example does not match what the fixed text promises. If the text says "your order number" and the example shows a date, the system detects the inconsistency.

None of these causes is serious on its own. They are all resolved by editing the template, not by creating a new account or changing your number.

How to fix it step by step

These steps can be done by the business owner or someone on the team without technical knowledge, from the WhatsApp Business panel or from the tool you use to manage templates.

1. 1Go to the templates section of your account and open the rejected template. You will see the reason for rejection as returned by Meta.
2. 2Locate each variable in the template (the slots {{1}}, {{2}}, etc.) and look at what example you loaded for each one.
3. 3Review the data type you declared for that variable and compare it with the example. If you declared number, the example must be a number; if you declared date, it must be a date with a clear format; if it is text, it must be realistic text.
4. 4Replace the example with a real value from your business. If the variable is the customer name, put a name; if it is the order number, put an order number with the format you actually use.
5. 5Remove from the example any character that is not part of the data: quotation marks, line breaks, decorative asterisks or emojis that will not be in the real message.
6. 6Verify that the example is consistent with the fixed text of the template. If the text says "your appointment on", the example must be a date or time, not a name.
7. 7Save the changes and resubmit the template for review.
8. 8Wait for Meta's response. The template approval period is up to 48 hours; there is no way to speed it up on your end.

How to prevent it from happening again

Once you understand how the example works, rejection for this reason almost disappears. These practices greatly reduce the probability of it happening again.

• Always load an example with real data from your business, not a placeholder. If you sell pizzas, the product example should be "muzzarella", not "product".
• Keep the same data type between the example and the actual use. If the variable will hold a phone number, the example must be a phone number in the format you use.
• Avoid decorative characters in the examples. Emojis and symbols go in the fixed text, not inside the variable example.
• Check the consistency between the fixed text and the example before sending. One minute of reading avoids a 48-hour wait.
• If you have several templates, build a base template that you already know works and use it as a reference for new ones.

When the real problem is something else and this rejection is just the symptom

Sometimes the rejection for example format is the tip of the iceberg: Meta is telling you something deeper about the template. If you fixed the example and it gets rejected again, look at these signals.

• The template has too many variables together. If you put five variables in a single sentence, the example for each one becomes hard to validate. Split the content into simpler sentences.
• The template category doesn't match the content. A promotional template declared as transactional is usually rejected, and the reason Meta shows may not be the real one.
• The fixed text is ambiguous. If the message doesn't make clear what goes in each gap, the example won't clarify it either.
• You're using a template for something it's not meant for. If the message is a reply to a customer within an open conversation, you may not need a template.

In those cases the fix isn't the example: it's rethinking the template. Sometimes it's better to split a complex template into two simpler ones, or change the category, or simply not use a template for that message.

What not to do when a template gets rejected

There are reactions that make the situation worse. These are the most common and it's best to avoid them.

• Don't create an identical new template to "try your luck". You'll accumulate rejections and waste time.
• Don't change the number or open a new account. The rejection has nothing to do with your account.
• Don't delete the rejected template without first reading the reason. The rejection information is what tells you what to fix.
• Don't resend the same template without changes hoping it will pass. The system will reject it again for the same reason.

How to check the status of your templates if you use Wando

If you manage your templates from Wando, you can see the status of each one and the approved, pending and rejected templates in a single place, along with campaigns and contacts. That helps you keep track of which template is stuck and why. Wando uses Meta's official WhatsApp API, so the approval process and timelines are the same as the ones you see in your Meta account.

Frequently asked questions

These are the questions that come up most often when Meta rejects a template because of the format of the sample.