WhatsApp Logs
The WhatsApp Logs section provides a comprehensive record of all automated interactions processed by the WhatsApp Cloud API Chat & Marketing module. This includes campaign deliveries, bot-triggered responses, and template-based messages. Use this section to monitor activity, troubleshoot delivery issues, and maintain a full audit trail of your WhatsApp communications.
Accessing WhatsApp Logsโ
Navigate to WhatsApp Module > WhatsApp Logs from the Perfex CRM sidebar. The logs are displayed in a sortable, searchable table that shows all automated message activity.
Log Table Columnsโ
Each log entry contains the following information:
| Column | Description |
|---|---|
| # | A unique auto-incremented ID for each log entry |
| Category | The type of automated interaction โ e.g., Marketing Campaign, Template Bot |
| Name | The name of the campaign, bot, or automation that generated the log entry |
| Template Name | The WhatsApp message template used for the interaction |
| Response Code | The HTTP response code returned by the WhatsApp Cloud API (e.g., 200 for success, 400 for bad request) |
| Type | The recipient type โ e.g., Leads, Customers, Contacts |
| Recorded On | The date and time when the interaction was recorded |
| Actions | Available actions for each entry: View details or Delete the log record |
Understanding Response Codesโ
The response code column helps you quickly identify whether messages were delivered successfully or encountered errors.
| Response Code | Meaning | Action Required |
|---|---|---|
| 200 | Success โ message accepted by WhatsApp API | No action needed |
| 400 | Bad Request โ invalid parameters or template issue | Review the template and parameters |
| 401 | Unauthorized โ invalid or expired access token | Regenerate your access token in Meta Business settings |
| 403 | Forbidden โ insufficient permissions | Check your System User permissions |
| 404 | Not Found โ invalid phone number ID or endpoint | Verify your Phone Number ID in module settings |
| 429 | Rate Limited โ too many requests sent | Reduce send frequency; retry after cooldown |
| 500 | Internal Server Error โ WhatsApp API issue | Retry later; check Meta status page if persistent |
A successful response code (200) confirms that the WhatsApp Cloud API accepted the message for delivery. It does not guarantee final delivery to the recipient's device โ delivery confirmation comes through webhook status updates visible in the chat interface.
Filtering Logsโ
Use the built-in filters to narrow down log entries and find specific records quickly:
- Category โ filter by interaction type (Marketing Campaign, Template Bot, etc.)
- Response Code โ filter by success (
200) or specific error codes - Type โ filter by recipient type (Leads, Customers, Contacts)
- Date Range โ select a start and end date to view logs within a specific time period
- Search โ free-text search across campaign names, template names, and other fields
Viewing Log Detailsโ
Click the View action on any log entry to see the full details of the interaction, including:
- Complete request payload sent to the WhatsApp API
- Full API response body
- Recipient phone number and contact reference
- Template parameters and variable values used
- Timestamp with timezone information
This detailed view is invaluable for troubleshooting failed deliveries or auditing specific message content.
Deleting Log Recordsโ
To remove individual log entries:
- Click the Delete action on the target log row.
- Confirm the deletion when prompted.
To bulk-delete logs, use the checkbox selection to select multiple entries and click Delete Selected.
Deleted log records cannot be recovered. If you need to retain records for compliance or auditing purposes, consider exporting the data before deletion.
Best Practicesโ
- Review logs regularly โ check for failed deliveries (non-200 response codes) and address issues promptly to maintain campaign effectiveness
- Monitor rate limits โ if you see frequent
429responses, reduce your campaign send rate or stagger deliveries across longer time windows - Keep tokens current โ
401errors indicate your access token has expired or been revoked; update it immediately to restore functionality - Archive before cleanup โ before deleting old logs, export or document any records needed for compliance, reporting, or dispute resolution
- Use filters for auditing โ when investigating a specific campaign or bot, use the Category and Name filters to isolate the relevant log entries quickly
WhatsApp Logs only capture automated interactions (campaigns, bots, template sends). Manual chat messages between staff and clients are stored in the chat history and are not duplicated in this log section.