WhatsApp Cloud API · error code

WhatsApp error 130472: User's number is part of an experiment

Permanent - do not retryHTTP 400Recipient & delivery

Last verified against Meta for Developers - Cloud API error codes

What WhatsApp returns
Message was not sent as part of an experiment.

What error 130472 means

Code 130472 is one of the stranger errors in the reference because nothing you did caused it. Meta runs marketing message experiments in which a slice of WhatsApp users is deliberately held out from receiving marketing template messages so that Meta can measure the incremental effect of those messages. When you try to send a marketing template to a user in the holdout group, the send is refused with 130472 and the message is not delivered or billed.

The error only affects marketing-category templates. Utility, authentication, and service messages to the same person go through normally. It is also per recipient and tied to the experiment's duration, so the same number will accept marketing again once the experiment ends.

There is nothing wrong with your template, your account, or the recipient's WhatsApp installation. Retrying immediately will produce the same response.

Why it happens

  • The recipient is in the control group of a Meta marketing message experiment.
  • The message uses a template categorized as marketing, which is the only category the experiment withholds.
  • A campaign list includes a small random fraction of held-out users, so the error appears sporadically rather than for everyone.

How to fix WhatsApp error 130472

  1. 1Log the recipient and skip them for this campaign; do not retry the marketing template.
  2. 2If the content is genuinely transactional, send it as a utility template instead, which is not withheld.
  3. 3Review Meta's Marketing Message Experiment documentation to understand the experiment's scope and duration.
  4. 4Track the share of 130472 responses per campaign so the holdout size is visible in your reporting and not mistaken for a delivery problem.

How to stop it recurring

Build campaign reporting that treats 130472 as a distinct outcome rather than a failure, so metrics and retries behave correctly. Keep transactional content in utility templates, which are unaffected. Because this comes from Meta's side, there is no configuration to change on yours; the goal is to stop it from triggering alerts or retry loops. Because it arrives in the statuses webhook like other delivery-time failures, correct webhook handling matters - see the webhook debugging guide - and compare 131049, Meta's other deliberate marketing drop.

Official reference: Meta for Developers - Cloud API error codes. See all WhatsApp error codes or the WhatsApp limits and quotas.

Related codes

Error 130472 - quick answers

What does WhatsApp error 130472 mean?

Code 130472 is one of the stranger errors in the reference because nothing you did caused it. Meta runs marketing message experiments in which a slice of WhatsApp users is deliberately held out from receiving marketing template messages so that Meta can measure the incremental effect of those messages.

How do I fix WhatsApp error 130472?

1. Log the recipient and skip them for this campaign; do not retry the marketing template. 2. If the content is genuinely transactional, send it as a utility template instead, which is not withheld. 3. Review Meta's Marketing Message Experiment documentation to understand the experiment's scope and duration. 4. Track the share of 130472 responses per campaign so the holdout size is visible in your reporting and not mistaken for a delivery problem.

Should I retry after error 130472?

No. Retrying the same request produces the same error; the condition has to be fixed first. Treat it as a permanent failure for that message and surface it, rather than looping.

Stop debugging WhatsApp by hand

Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.