On this page

Meta publishes per-template sent, delivered, read and per-button-click figures, and VGraple CRM pulls them into the same screen as everything else you manage a template from, alongside a workspace-wide approval rate that tells you whether the pre-submission validator is actually catching what Meta rejects.
Template analytics: first 5 of 6 steps
- 1Open a template to see its own
- 2Read the sparkline
- 3Watch for the falling read-rate warning
- 4Check button clicks, if the template has
- 5Check the workspace-wide approval summary
Before you start
- Template performance data requires the connected WhatsApp Business Account to have analytics enabled at Meta's end; this is a WABA-level setting, not something VGraple CRM configures.
- You need "View templates" permission to see either the per-template performance chart or the workspace-wide approval summary.
- Analytics sync runs automatically once a day; there is no manual trigger, since it is a background job rather than a per-visit pull.
Steps
- Open a template to see its own performance. Click any approved, paused or disabled template from the Templates list. A Performance card shows the last 30 days: total Sent, the percentage Delivered and the percentage Read, with a day-by-day bar chart underneath.

Read the sparkline. Each bar's height reflects that day's send volume, and its opacity reflects that day's read rate, so a quick glance shows both volume and engagement at once. Hovering a bar shows the exact date, sent count and read count.
Watch for the falling read-rate warning. When there is enough recent volume on both sides of the tracked window to compare meaningfully, a note appears if the read rate has dropped by a third or more against the earlier half: "The read rate is falling. WhatsApp pauses templates whose recipients stop engaging, so consider what changed before it acts." This is silent when there is not enough data to say anything reliable, rather than guessing from too little traffic.
Check button clicks, if the template has any. Below the chart, each button's click count is listed by its label, pulled from the same Meta analytics feed.
Check the workspace-wide approval summary. Above the Templates list, once you have at least three decided submissions in the last 90 days, a bar shows your approval rate as a percentage of decided submissions, and, if any were rejected, that count too.
Read the pre-submission check accuracy. Alongside the approval rate, a second figure shows what percentage of templates the validator called low risk were rejected by Meta anyway ("false negatives"), plus how many rejected templates the validator did warn about first, for contrast.
What you will see
A template with no sends yet, or one sent too recently for Meta to have reported figures, shows "No figures yet. WhatsApp reports per-template performance a day after the first sends, and it appears here automatically" instead of a misleading row of zeros. A template with real send volume shows the full performance card described above.
Settings and options
| Setting or field | What it does | Default |
|---|---|---|
| Analytics sync | Pulls Meta's sent, delivered, read and button-click figures for every eligible template | Runs automatically once a day |
| Lookback window | How far back the sync pulls figures | 80 days (Meta's own maximum) |
| Approval rate window | The period the workspace-wide approval summary covers | Last 90 days |
| Approval summary visibility threshold | Minimum decided submissions before the summary appears | 3 |
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| "No figures yet" on a template sent weeks ago | Analytics may not be enabled on the connected WhatsApp Business Account at Meta's end | Confirm analytics is enabled for the WABA in Meta's own account settings; this is outside VGraple CRM's control |
| Figures show zero for a template sent an hour ago | Meta reports template analytics roughly a day behind | Wait; a template sent today typically appears here tomorrow |
| Read rate warning appears on a template that is clearly doing fine | The warning only fires when there is enough send volume on both halves of the comparison window to mean something; a real dip is the more likely explanation once it appears | Review recent sends and recipient list quality for that template |
| Approval summary never appears | Fewer than 3 decided submissions in the last 90 days | Submit and wait for Meta to decide on at least 3 templates; the summary appears automatically once that threshold is reached |
| Button click counts show nothing for a template with URL buttons | Clicks are reported by the same daily Meta sync and lag by roughly a day like the other figures | Wait for the next day's sync; clicks are not tracked separately from the main analytics pull |
Related reading
A falling read rate is the earliest signal that a template is heading toward a pause; see template paused or disabled by Meta for what happens next and how VGraple CRM protects a running broadcast when it does.