Reports & measurement
Read campaign outcomes, compare meaningful periods and separate activity from customer results.
Define the population, time zone, time range and event before comparing numbers. Separate operational delivery from business outcomes such as enquiries and completed sales.
Choose a report period
Make the time scope of an analysis explicit.
Use a custom date range
Inspect a specific business period without assuming calendar-month boundaries.
Open a specific campaign report
Connect an aggregate result to the exact campaign that produced it.
Read a delivery funnel
Understand the meaning of each visible message state.
Calculate a delivery rate consistently
Use a defined denominator for a meaningful percentage.
Report pending outcomes honestly
Keep incomplete results visible during an active campaign.
Group campaign failures by reason
Identify useful corrective work from delivery errors.
Compare two campaigns fairly
Control for audience, content and time differences before drawing conclusions.
Separate replies from sales conversion
Avoid treating conversation activity as confirmed revenue.
Review contact growth separately from permission
Track database size without overstating campaign-ready reach.
Interpret an audience preview count
Understand what a pre-send matching count does and does not mean.
Review template availability over time
Understand how approval or pausing affects campaign readiness.
Understand report freshness
Recognise when a view may lag behind the underlying event.
Compare reports across devices
Check whether two views use the same filters and account context.
Prepare a client-facing performance summary
Explain results in plain language with clear limitations.
Avoid misleading averages
Use measures that reflect the operational question.
Review support workload from conversations
Use operational evidence without assuming every message is a new case.
Read team activity in context
Understand actions without equating screen presence with productivity.
Keep report screenshots private
Share evidence without exposing unnecessary customer information.
Document the meaning of a business metric
Make recurring reports consistent across the team.
Review a campaign with no replies
Investigate relevance and next steps without assuming technical failure.
Reconcile report data with a support case
Give support a precise example of an apparent mismatch.
Review subscription usage separately from outcomes
Distinguish resource consumption from customer success.
Create a weekly communications review
Use a repeatable agenda to improve operations.
Explain the limits of attribution
Avoid crediting every business outcome to the latest message.
Relevant public sources
- WhatsApp Business Platform pricingProvider pricing
- Alactic Communications Terms & ConditionsAlactic public terms