Conversion-measurement readiness for Marketing Messages

GET 
/api/channels/:channel/whatsapp/marketing-readiness

Whether Meta can attribute WEBSITE conversions to the marketing messages this WhatsApp number sends through the Marketing Messages API. Meta does that by itself when the template's button opens a page that reports through Meta Pixel or the Conversions API, into a dataset in the same business portfolio as the WABA.

Calls no Meta endpoint. It reads the channel's mirrored onboarding status, the workspace's own Conversions API settings (never the token), and the Meta Pixel ids found on the workspace's connected web sites — by fetching each site's home page and the Google Tag Manager containers it loads, through the SSRF guard, with short timeouts, cached for six hours (fifteen minutes after a failed fetch). refresh=1 re-reads the sites, at most once a minute. A site that could not be read is unknown, never not_found. The business-portfolio condition cannot be verified through the API and is always returned as manual. Admin-gated (Channel view); 404 for a channel that is not WhatsApp.

Request

Responses

200

The readiness checklist.

401

Not authenticated. code: account_disabled means the member's seat was deactivated in this workspace: the session is over even though the token was not revoked (clients sign out and clean up).

403

Authenticated but not allowed.

404

Resource not found (or not visible to the current tenant).