Template Analytics

Measuring template performance: sent, delivered, read, and clicked metrics.

What It Covers

Template analytics helps measure how each template performs over time. Typical metrics include:

  • Sent — total messages sent
  • Delivered — confirmed deliveries
  • Read — confirmed read receipts
  • Clicked — CTA button clicks (for applicable templates)

Metric availability and endpoint shape can vary by provider. Use the analytics endpoint exposed by your stack (Meta direct or BSP route).

Example Query

GET /whatsapp_business_accounts/<WABA_ID>/template_analytics?start=1735689600&end=1738367999&granularity=DAY

Example Response

{
  "data": [
    {
      "template_name": "order_update_v1",
      "language": "en_US",
      "category": "UTILITY",
      "sent": 1240,
      "delivered": 1220,
      "read": 980,
      "clicked": 0
    },
    {
      "template_name": "welcome_offer_q1",
      "language": "en_US",
      "category": "MARKETING",
      "sent": 9500,
      "delivered": 9102,
      "read": 6022,
      "clicked": 1184
    }
  ]
}

When URL CTA templates are used, tracking parameters can be appended to links for analytics attribution. Validate this behavior in your own reporting flow before relying on click metrics for billing or campaign decisions.

For template structure details, see Template Elements.

Related

  • TemplatesTemplate lifecycle, categories, and management through Dualhook and Meta Graph API.
  • Template ElementsTemplate structure: headers, body, footer, buttons, variables, and practical limits.
Browse more docsGet started with Dualhook