How to Analyze Active Message Sends via WhatsApp – Blip | Blip Help

Introduction

After sending active messages, whether through the Growth module (via Portal or API) or through Blip Desk, it is essential to analyze the results obtained from the campaigns. Monitoring which customers received, opened, and engaged with the messages allows you to clean your contact base.

This data analysis process is strategic because it ensures that future sends are directed only to those who show genuine interest. The main benefits of this practice include:

Increased engagement: Your communication reaches a more qualified audience that is more likely to interact.
Cost optimization: You avoid spending your send quota on inactive numbers or disengaged users.
Preservation of channel quality: Protects your number’s reputation and prevents penalties or blocks from providers, ensuring quality maintenance.

Prerequisites:

Data validation must be done exclusively on the bot that is directly connected to the WhatsApp channel;
If your intelligent contact uses a router and sub-bots architecture, verification must be done on the router, as this is where your WhatsApp channel will be connected.

How to Monitor Active Message Sends

Currently, there are three main ways to analyze the campaign sends:

Through the active messages dashboard in the Analysis module;
Through the campaign report in Growth;
Through the Active Messages report in the Report Manager;

1. Through the active messages dashboard in the Analysis module:

To view metrics via the Analysis module, follow the steps below:

1. Access the portal;
2. Then access the bot connected to the WhatsApp channel;
3. Select the “Analysis” tab;
4. Within Analysis, click on the "Active Messages" dashboard.
5. Filter by the desired period or date;
6. Or search by the template name whose send you want to analyze:

Information Available on the Analysis Screen

On the screen, an overview with the main performance data is available, organized into cards and interactive graphs:

Total messages sent: View the total volume of messages sent in the selected period.
Conversion funnel: Understand the contacts’ behavior from message receipt to response.
Conversion: Check the volume of messages that generated interest among your contacts compared to the total sent or that failed.
Conversion rate: Track the percentage of active messages that generated a response from the contact.
Failure rate: Identify the proportion of messages that were not delivered and the main reasons for failure.
Response peaks: Discover the times when messages receive the highest response rates.
Send failures: Identify errors and occurrences of messages that failed.

Note on Data Updates: The data on this dashboard is updated on D-1. During the first days of the month, data may show slight variations until the period is fully closed.

2. Through the campaign report in Growth:

1. Access the ‘Growth’ tab of your bot connected to WhatsApp;

2. Select ‘Active messages’;

3. Then select ‘Send summary’:

On this screen, the list will display the following data about the campaigns:

Campaign name: Title defined at creation. For campaigns sent via Blip Desk, the default starts with Desk-Active-Campaign followed by an alphanumeric code.
Message status: Consolidated view of the number of messages sent, failed, received, read, and responded for that send.
Scheduling: Date and time when processing started. Immediate campaigns show "No scheduling".
Send date: Date and time when the send was actually performed. Scheduled sends not processed show the status "Waiting".

You can filter campaigns/sends by:

Channel (WhatsApp, GoogleRCS, and other channels);
Message type (All, scheduled, unscheduled);
Campaign type (All, Individual, or batch)
By the campaign name you want to search for:

Monitoring Message Status via Growth

To track your campaigns’ performance, observe the data in the Status column:

It will display the following returns for the sent messages:

Audience: total number of valid phone numbers in the audience;
Failed: The message could not be delivered to the client. (For more information, see the documentation: Active message send failures: Where to find and what they mean )
Received: The message successfully reached the user’s device.
Read: The client opened the message.
Responded: The client interacted and replied to your send.

Important about status updates: It is important to note that updating these returns depends directly on information sent by Meta regarding the end user’s device behavior.

Thus, if a message shows the status PROCESSED, don’t worry: this indicates that the send was successfully completed by Blip and the system is just waiting for Meta to update the client’s final status.

Campaign Report (CSV Export)

You can also analyze send details by downloading a CSV file. To do this, still on the Send summary screen:

1. Click the three dots after the campaign you want to get the report for;
2. Select ‘Download report’:

The exported CSV file contains detailed raw data of your campaign send. Below is a description of each column in the report to facilitate your analysis:

General Campaign Data

Date: The date and time the campaign was sent
Campaign ID: The unique identification code generated by the system for this campaign.
Campaign name: The title you defined when creating the send.
Message template: The name of the template/message model used in this send.
Sent by: Identification of the user, system, or router responsible for sending the campaign.
Channel: The communication channel on which the campaign was executed (e.g., WhatsApp).

Contact Information

Contact identity: The unique user identifier within the channel on Blip (on WhatsApp, usually in the format number@wa.gw.msging.net).
Contact phone: The end customer’s phone number based on the ‘Phone’ field within the platform.

Performance and Status

Message status: The current state of the message (e.g., processed, failed).
Sent: Shows the time the message was sent by the Blip platform.
Received: Shows the time the message was successfully delivered to the user’s device.
Read: Indicates the time the client opened/viewed the message in the app.
Response routing: If it is a campaign sent via Blip Desk, shows the agent who received the response.

Error and Failure Details

Failure: Indicator confirming whether a failure occurred in the send attempt to that specific contact.
Failure code: The internal Blip numeric code related to the processing issue.
Failure description: A brief explanation of why the send failed internally.
Error code: The numeric code returned directly by the channel provider (such as Meta) explaining the reason for rejection.
Error group: The category the failure falls into (e.g., device unavailability, permission restriction, number format error).
Error message: The exact technical text returned by the channel API detailing the occurrence.
Error description: A clearer explanation about the reported problem and the context of what caused it.

For more information on this topic, see the documentation: Active message send failures: Where to find and what they mean

3. Through the Active Messages report in the Report Manager:

This report provides active message data separated into two tables:

The Notifications summary table with detailed data of sent active notifications.
The Notifications Users table with summarized data, usually grouped by template and bot.

To download it, follow these steps:

1. Access the portal;

2. Then access the bot connected to the WhatsApp channel;

3. Select the “Analysis” tab;

4. Within Analysis, click on "Report Manager";

5. In ‘Choose a chatbot to extract data’, select the same chatbot where you are performing the action, as data will only be extracted from the bot connected to the channel;

6. In ‘Select report period’, filter by the desired period.

Important: You can extract data from up to 5 years ago, for periods of 90 days. If you select a period longer than 90 days, the report will not be generated correctly.

7. In ‘Define report type’ select ‘Active messages;

8. Finally, select “Generate Report’.

9. To view your report, check the ‘My Reports’ field. In the ‘Report’ column, it will be displayed as ‘Active Messages’;

10. Click ‘Download report’:

Tips and FAQ

What are the benefits of analyzing and cleaning my base?

The practice of directing messages only to those who show real interest generates the following benefits:

Increased engagement: Your communication reaches a more qualified audience that is more likely to interact.
Cost optimization: You avoid spending your send quota on inactive numbers or disengaged users.
Preservation of channel quality: Protects your number’s reputation and prevents penalties or blocks from providers, ensuring quality maintenance.

Status "PROCESSED": What does it mean?

Status updates depend directly on information sent by Meta about the end user’s device behavior. Therefore, if a message shows the status PROCESSED, don’t worry: this indicates that the send was successfully completed by Blip and the system is just waiting for Meta to update the client’s final status.

Where can I find more details about failure reasons?

For more information about delivery failure causes, see the complementary documentation: Active message send failures: Where to find and what they mean

"My data doesn’t match the Growth screen." Why?

The data shown on the two screens do not match due to differences in how they are counted:

Growth: Counts all messages processed by Blip (sent, received, failed, read, and responded).
Active messages dashboard: Shows only messages actually processed by Meta.

Practical example:

If you send two active messages, and one is successfully delivered by Meta but the other fails at Blip, the Growth screen will show 2 messages, while the Active Messages screen will show only 1, as only one was successfully completed by Meta.

Why doesn’t the sum of received and failed messages match the total messages sent?

Not every sent message receives an immediate delivery or definitive failure status from Meta (WhatsApp). There is a technical interval, often called the "limbo," which can represent up to 4% of the total sends. Meta has up to 20 days to process and update the status for held messages. The most common reasons include:

User Offline: The recipient is out of coverage area, without internet connection, or the phone is off.
Brand Block: The user blocked your company’s number. Meta does not disclose the specific reason to protect the end user’s privacy.

Practical Example of Calculating and Validating the "Limbo":

To validate whether your metric is within the expected operational margin (up to 4%), use the following steps based on a real scenario:

Identify Total Sent: In this example, we use 1,413.
Identify Total Received: In this example, 1,146.
Identify Total Failures: In this example, 218.
Sum Known Statuses: Add Received + Failures (1,146 + 218 = 1,364).
Calculate the Difference: Subtract the sum from the previous step from Total Sent (1,413 - 1,364 = 49 messages).
Calculate the 4% Margin: Multiply Total Sent by 0.04 (1,413 * 0.04 = 56.52).
Compare the Results: Since 49 is less than the limit of 56.52, the data in this scenario is technically validated and within normal range. If the difference exceeds 4%, we recommend contacting technical support for investigation.

How to ensure successful cleaning?

Cross-check Received, Read, and Responded data with the total Audience. Isolate contacts who are not interacting and remove them from future distribution lists. This ensures the health of upcoming sends and prevents blocks.

Need more help? Explore our content at Blip Academy or Blip Community, watch tutorials on our YouTube channel, or get your questions answered on our support channel 😃