Automatic Events API | Developer Documentation

Automatic lead and purchase events: ChatArchitect availability

ChatArchitect does not support Automatic Events API: automatic identification of leads or purchases in conversations started from Click-to-WhatsApp ads, followed by reporting those events to Meta Conversions API. This availability was confirmed on 4 October 2026.

What this means for your connection

Connecting a WhatsApp number through ChatArchitect's prepared signup does not activate this advertising workflow. Do not plan a campaign on the assumption that ChatArchitect will detect a conversion from the conversation or send it to Meta automatically.

• An incoming customer message is a communication event. It does not by itself establish a qualified lead or a completed purchase.
• A message delivery result describes a sending attempt. It does not confirm a conversion, payment or sale.
• A Meta setting or developer example does not establish that the corresponding event is available in your ChatArchitect integration.

The automatic_events receiving guide explains this distinction for applications expecting callbacks. Use the ChatArchitect webhook guide for documented incoming messages and outgoing results.

Plan lead and purchase tracking in your own workflow

If you need conversion reporting, first identify the business action you want to measure: an inquiry, a qualified lead, an order or a completed payment. Specify which system records that action and what evidence confirms it.

1. Check how your connected CRM or help desk records the conversation and any lead or order. The available actions depend on the integration and the receiving system.
2. Keep a chat, a CRM stage change and a completed purchase separate in your reporting rules.
3. For a separate advertising or analytics integration, confirm its supported event source, account, field mapping and duplicate handling with its provider before relying on it.

This checklist does not promise a conversion-reporting connector or an alternative Conversions API service from ChatArchitect. Support for a separate tracking arrangement must be established for that arrangement.

When you need help

Tell ChatArchitect support which CRM or application you use, the business action you want to record and the advertising/reporting destination. For a missing ordinary message, include the affected connection, time with time zone and the receiving result. Do not send App keys, Secrets or unredacted customer conversations.

Separate Meta developer references

Organizations building their own Meta integration should consult Meta's Automatic Events API documentation and its automatic_events webhook reference. These describe a separate developer interface; their presence does not make this workflow available through ChatArchitect.