Skip to main content
Proactive messages and campaign sends, with the delivery funnel timestamps and the provider error when a send failed.

One row is

one outbound message

Delivery

Rewritten daily

Columns

32

Where it lands

The partition delivered today holds the whole table. Read the latest snapshot_date= partition only, and check for _SUCCESS before you do, as described in bucket layout.

Columns

bigint
Internal warehouse key. Not stable between deliveries — the send is identified by conversation_id.
varchar(36)
Identifier of the workspace the send belongs to.
varchar(256)
Id of the tenant. NULL for rows with no tenant mapping.
varchar(256)
Name of the tenant. NULL for rows with no tenant mapping.
bigint
Internal warehouse key for the contact. Join cloud_chat_contacts through the conversation instead.
bigint
Join key. Conversation the message opened or belongs to. Joins to cloud_chat_conversations.
bigint
Number shown to agents for that conversation.
bigint
Inbox the message was sent from.
varchar(65535)
Name of that inbox.
bigint
Campaign the send belongs to. NULL when outbound_source_type is individual_proactive.
varchar(255)
Name of the campaign.
varchar(65535)
Name of the audience the campaign targeted.
varchar(256)
Name of the WhatsApp template used in the send. For campaign, the template configured on the campaign; for individual_proactive, the first template sent in the conversation. NULL for a free-text send.
varchar(64)
Category of the template as declared when it was sent: MARKETING, UTILITY or AUTHENTICATION. Campaign sends do not record it, so it is usually NULL for campaign. For what Meta charged, use meta_pricing_category.
boolean
billable as reported by Meta for the template message of this send. Meta is phasing this field out: read meta_pricing_type and meta_pricing_category together instead.
varchar(64)
Category Meta billed the template message of this send under: marketing, utility, authentication, authentication_international, service or referral_conversion. Recorded since November 2026. NULL for older sends, for sends whose message was never delivered, and when the template message of the send cannot be found in the conversation.
varchar(64)
regular when Meta charges the template message of this send at the rate of meta_pricing_category; free_customer_service or free_entry_point when it costs nothing.
varchar(64)
Meta pricing model the template message of this send was billed under. PMP, per-message pricing.
varchar(20)
What produced the send: campaign for a bulk send, individual_proactive for one agent reaching out to one contact.
timestamp
When the send was created in the workspace.
timestamp
When the provider accepted the message. NULL when it never went out.
timestamp
When the message reached the contact’s device.
timestamp
When the contact opened it. Always NULL on channels that do not report read receipts, which is not the same as unread.
timestamp
When the contact replied.
boolean
Whether the message was sent. The funnel starts here.
boolean
Whether it was delivered.
boolean
Whether it was read.
boolean
Whether the contact replied. The four flags give you the delivery funnel without comparing timestamps for NULL.
varchar(6)
Provider error code when the send failed. NULL on successful sends.
varchar(97)
The error code with a plain-language explanation, for example a rate limit, a policy block or an undeliverable number. Other error covers codes without a specific category.
timestamp
When the datamart last wrote this row.
date
Partition column. Date of the delivery that wrote this file, in YYYY-MM-DD.