Measurement Partners | Developer Documentation

Prepare a WhatsApp measurement brief for an external analyst

Start with the question you want the analyst to answer and the evidence available in your connected tools. Meta's Measurement Partner registration is a separate developer arrangement; it is not a prerequisite for comparing data you already have from a ChatArchitect connection.

Define the business question

Choose a specific outcome, such as a customer reply, a qualified lead or a completed sale. Record what your business counts as that outcome, its reporting period and which system records it. A delivered message, a website visit and a sale are different observations.

Prepare a source list

Use the report comparison guide to record each source's time zone, counting unit, number and filters. Mark an unavailable measure as unavailable; it is not a measured zero.

Agree on what can be compared

• Identify the number, campaign and period included in each dataset.
• Use source references that the tools actually provide. Confirm a join before treating a chat as belonging to a particular ad or sale.
• If a reliable join is unavailable, describe the reports separately rather than claiming a person-level conversion path.
• Agree on the fields the analyst needs and use an appropriate export or report-sharing route. Issued ChatArchitect API secrets are not report-sharing credentials.

Check a small example before requesting a larger report

Pick an agreed campaign and a small reporting period. Ask the analyst to show the source, definition and calculation for each result. Investigate mismatched totals using the source list before changing the campaign or connection.

ChatArchitect does not provide Automatic Events API to infer ad-driven leads or purchases and send them to Meta Conversions API. That limitation does not settle every other advertising integration. Confirm any separately proposed measurement implementation and its access requirements with the responsible provider.