> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://myoperator.crisp.help/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# What is the correct way to use parameters in the MyOperator app for WhatsApp templates?

## Quick answer

Use double-brace placeholders — {{1}}, {{2}}, {{3}} — in your template body (and header text/button URLs if needed). Provide matching sample values in square brackets when submitting the template, then map each column from your Excel/CSV file to the placeholders during campaign setup. Parameters are not allowed in the footer.

## When should I use this guide?

Use it right before you create or submit a WhatsApp Template Message that requires personalisation (names, order IDs, dates) so you avoid Meta rejections and blank variables.

---

## 1. What parameters are

* Written as {{1}}, {{2}}, {{3}} (variables/placeholders)
* Replaced with real values pulled from your Excel/CSV audience file at send-time.
* Sample values are mandatory for Meta review.

---

## 2. Step-by-step: add parameters to a template

1. Login to MyOperator Panel → Go to WhatsApp → Templates → Create New Template.

2. Insert parameters where you need personalisation.

1. ✅ Correct: `Hello {{1}},` Enjoy an exclusive `{{2}}` discount on your next purchase with us! Renew Before `{{3}}`

2. ❌ Incorrect: `Hello {1},` Enjoy an exclusive 2 discount on your next purchase with us! Renew Before 3.

![](https://content.api.getguru.com/files/view/6820c7c5-d915-44f2-93d0-8beea85b40f0)

*Alt text: Sample parameter insertion in the template*

3. In the Sample Message, replace each variable with a realistic placeholder in square brackets.

   Example: `Hello [John], your order [#12345] is out for delivery.`

4. Please submit the template; the Meta review requires both the template format and a sample value.

---

## 3. Quick reference table

| Stage | Format Example | Output Example |
| ---- |
| Template format | `Hello {{1}}, your order {{2}} is confirmed.` | {{1}} = customer_name, {{2}} = order_id |
| Sample message | `Hello [Rahul], your order [#B456] is confirmed.` | Submitted to Meta for approval |
| Live campaign | (after sending) `Hello Rahul, your order #B456 is confirmed.` | Actual customer-facing message |

---

## 4. Approval rules & restrictions

* Parameters allowed only in:
* Header (text only)
* Body
* Buttons (URL query strings, CTA labels)

* Not allowed in the footer.

* Must appear sequentially ({{1}}, {{2}}, {{3}}… no skipping).

* Every parameter in the template format must have a sample value.

---

## 5. Best-practices checklist

* ✔ Provide clear sample values `[Priya]`, `[Order #12345]`.
* ✔ Keep messages conversational; avoid robotic tone.
* ✔ Preview the template before submission.
* ✔ Use fallback values during campaign mapping (e.g., “Customer” if name missing).
* ✔ Limit the number of parameters; too many may be rejected for poor user experience.

---

## 6. Summary

* Parameters personalise messages and are required for certain template approvals.
* Define them with `{{n}}` and supply sample values in `[ ]`.
* Follow Meta’s rules: sequential numbering, no parameters in footers, and provide matching samples to avoid rejection.

---

Keywords: WhatsApp parameters, {{1}} {{2}}, sample values, variable mapping, MyOperator