Statistics

The Chat Statistics section provides a visual and data-driven overview of your campaign performance and channel usage. This dashboard is essential for monitoring engagement levels and understanding billing categories.

Date Range Selector: At the top of the dashboard, you can filter data using the From and To date pickers. To ensure optimal performance and granular reporting, the system allows for custom date selections, typically recommended for periods of 90 days or less.

Visual Performance Indicators: Below the filters, the General statistics section displays the total volume of messages delivered, categorized by their specific purpose and billing impact. Each category is represented by a highly visual circular progress chart:

  • Authentication & International: Monitors security-related messages, such as OTPs or login verifications.
  • Marketing & Marketing Lite: Tracks promotional and high-value customer engagement campaigns.
  • Referral: Captures interactions initiated through referral entries.
  • Service & Utility: Displays operational communications and customer support interactions.

Billing Transparency: Categories marked as billable provide direct insight into your platform usage costs according to the WhatsApp Business policy.

Notifications received per day

This graph tracks the lifecycle of your notifications by measuring Sent, Delivered, and Read statuses. It allows you to monitor engagement trends and identify the peak times when your audience is most active.

notifications per day

Sending history

This stacked area chart provides a chronological view of your message volume. You can hover over any point on the timeline to see a detailed breakdown of message categories, such as Marketing, Service, or Utility, for that specific date.

Sending Logs

For a detailed audit of your activity, the Sending history table lists every interaction with the following data points:

  • IDs: Includes both the unique Sending ID and the associated Campaign ID.
  • Channel Confirmation: Displays the specific platform used, such as the WhatsApp icon.
  • Metrics: Tracks the exact number of messages Sent, Delivered, and Read, while flagging any Errors for immediate troubleshooting.

Data Export

You can download comprehensive reports by clicking the Download icon (blue circle with a downward arrow) located at the bottom right of the charts.

New Chat Field Mapping

The new Chat introduces an updated data export structure designed to simplify message direction tracking and align data reporting across all communication channels. The table below details the updated schema and value mappings between Chat v1 and New Chat for BigQuery eventChat exports:

Chat v1 Field (eventChat)New Chat FieldDescription
message.idchannelMessageIdUnique channel message identifier.
cs.instance_idapplicationIdIdentifier of the application instance.
message.send_typesendTypeReplaces generic input/output values with specific message directions: incoming (user messages), proactive (campaigns), or reactive (bot/agent replies).
cs.id / conversation_session_idcontactIdInternal system identifier for the contact.
cs.channelchannelTypeDelivery channel used.
cs.contact_idcontactCodeExternal contact identifier.
message.errorerrorDetails or payload for delivery errors.
message.integrationintegrationTypeService handling the dispatch.
message.processed_at / cs.created_atcreatedAtUnified event creation timestamp.

Export Data Dictionary

Here is an explanation of the fields included in the downloaded reports:

  • messageId: Unique numerical identifier for the message record.
  • campaignId: Identifier of the associated chat campaign (blank for non-campaign messages).
  • sendingId: Dispatch batch ID for scheduled or bulk send operations.
  • contactId: Internal system ID assigned to the contact.
  • contactCode: External identifier for the user (e.g., phone number, email, or custom user ID).
  • channelType: Delivery channel used for the message (e.g., web_chat, cloud_api).
  • content: JSON payload containing the message body, template variables, interactive buttons, or media links.
  • sendType: Directional classification of the interaction (input for user-initiated, output for platform/agent-initiated).
  • contentType: Format of the message payload (template, text, location, multimedia, redirection).
  • integrationType: Originating service handling the dispatch (sending for campaigns, pathbot for decision flows, auto_reply for automated triggers).
  • messageDate: Timestamp indicating when the message was recorded in the database (UTC).
  • scheduled: Target execution timestamp for deferred dispatches.
  • profileName: Name of the agent, profile, or virtual assistant handling the message.
  • sent: Timestamp indicating when the message left the gateway (UTC).
  • delivered: Timestamp confirming delivery to the end user's device (UTC).
  • read: Timestamp indicating when the contact opened/read the message (UTC).
  • error_at: Timestamp recording when a dispatch failure occurred (UTC).
  • error_type: JSON object containing error codes and diagnostic details if delivery failed.

CSV Report Field Mapping for WhatsApp Flows

When downloading message reports as .csv files for WhatsApp Flows and chat campaign statistics, use the following mapping table to align legacy Chat v1 export fields with the new Chat schema:

Chat v1 Field (Legacy)New Chat FieldBehavioral Status
messageIdmessageIdUnchanged.
messageDatemessageDateUnchanged.
sendTypesendTypeUnchanged.
contentTypecontentTypeUnchanged.
statussent, delivered, read, error_typeRestructured: Replaced by explicit lifecycle milestone columns.
statusAtsent, delivered, read, error_atRestructured: Individual stage timestamps replace the single updating timestamp.
channelExternalId(Removed)Deprecated in Chat v2.
errorerror_typeRenamed for clarity.
contentcontentUnchanged.
scheduleAtscheduledRenamed for clarity.
integrationintegrationTypeRenamed for clarity.
channelchannelTypeRenamed for clarity.
profileNameprofileNameUnchanged.
contactIdcontactIdUnchanged.
dfIntentId(Deprecated)Removed in Chat v2.
dfIntentName(Deprecated)Removed in Chat v2.
isFallback(Deprecated)Removed in Chat v2.
sendingIdsendingIdUnchanged.

Did this page help you?