WhatsApp API error 130472: User's number is part of an experiment
Error 130472 means WhatsApp deliberately didn't send a marketing message to this person because they're in a marketing message experiment that Meta runs. It isn't a fault in your message or your account.
Quick answer
The recipient is in Meta's marketing message experiment, so the message wasn't sent. Don't treat it as a failure to fix; record it and move on.What WhatsApp error 130472 means
Meta documents 130472 as: message was not sent as part of an experiment, and points to its marketing message experiment documentation. Some users are held out from receiving certain marketing messages so Meta can measure their effect.
Why error 130472 happens
The message itself was fine; something about the recipient or your relationship with them stopped it. Typical triggers:
- The recipient is in the group Meta holds out from marketing messages for its experiment.
- A marketing campaign reached users who are part of that experiment.
- A campaign sent to a large audience, which is more likely to include users in the experiment.
How to fix error 130472
There is no request change that gets this message delivered; the work is in your data and your audience.
- Record 130472 separately from real failures in your reporting.
- Don't resend the same marketing message to the person straight away.
- Keep sending utility and service messages they need as normal.
- When judging a campaign, exclude these users from delivery-failure rates.
- Explain 130472 in campaign reports, so it isn't read as lost messages.
Should you retry after 130472?
Don't retry: the message was intentionally not sent. Retrying won't change the outcome.
How error 130472 shows up in InfiQ
When the send is refused on the spot, the InfiQ API response holds Meta's error object unchanged (code 130472, the "(#130472)" message and error_data.details) alongside InfiQ's own InfiQ_traceid. When the failure only shows up after the send was accepted, it arrives as a message.failed webhook whose data.error.metaErrorCode is 130472, tied to the original message. Treat both the same way in your error handling. Keep the trace IDs with the failed message: they are what support needs to look it up.