Setting up conversion measurement | Developer Documentation

Measure a ChatArchitect WhatsApp marketing campaign

Start with a question you can answer using data your business already collects, such as how many campaign visitors submitted a form or placed an order. ChatArchitect customers send an approved Marketing template through a connected CRM, help desk or other sending tool. Whether Meta's separate Marketing Messages API conversion reports are available for those sends has not been confirmed. Do not assume that a ChatArchitect campaign will appear automatically in Meta Ads Manager or Insights API. See the marketing features guide for the confirmed customer workflow.

Set up a measurement plan before sending

1. Choose one outcome. Define the action to count, such as a completed order, booked appointment or qualified lead, and the period after the send in which you will count it. Record the campaign name, template and intended audience so you can compare the result with later campaigns.
2. Mark the destination. If a URL button is available in your template form and sending tool, point it to a page you control with a campaign identifier, for example https://example.com/offer?utm_source=whatsapp&utm_medium=message&utm_campaign=oct_offer. Use a different identifier for a different campaign. Do not put a customer's name, phone number or other personal data in the URL.
3. Test the complete path. Send the approved template to a permitted test recipient. Open the button on a phone, follow every short link or redirect, and check that the destination works and retains the campaign parameters. Complete a test action and confirm that your website analytics or CRM records it under the expected campaign. The link tracking guide explains how to check URL parameters and interpret website visits.
4. Note what each system can report. Check whether your connected sending tool shows sent and delivered results. Your website analytics can count visits to a tagged destination; your CRM or order system can count the chosen action. Check template quality in wtargeted.com using the quality guide. If a metric is unavailable, mark it as unavailable rather than zero. The metrics guide maps each indicator to its data source and explains how to compare reports.
5. Review on the same basis. Compare visits and actions for the same campaign identifier and time period. If your analytics links actions to visits, tracked visit-to-action rate is visits with the chosen action divided by tracked visits. Otherwise report the two counts separately. Check the ChatArchitect pricing guide and your actual charges before calculating cost per recorded action.

Interpret the result carefully

A tagged visit shows that a visitor reached the destination through that link; it does not prove that every recipient saw the message or that the message caused a later purchase. Website visits, WhatsApp delivery and business conversions are different measurements. A comparison group or a controlled test can help estimate the additional effect of a campaign when your analytics process supports it. Meta's marketing messages best practices recommend defining conversion events, testing and measuring outcomes across the customer journey.

The old version of this page described automatic Meta Pixel and Conversions API attribution, linked ad accounts and fbclid handling for direct Meta MM API use. Those steps are not established as ChatArchitect customer features. If you need Meta-specific click or conversion attribution, ask ChatArchitect support which reports and integrations are available for your account before building around them. The API scope guide explains the distinction.