{"id":784,"date":"2026-10-29T13:27:33","date_gmt":"2026-10-29T13:27:33","guid":{"rendered":"https:\/\/vectalk.com.br\/blog\/whatsapp-error-130472\/"},"modified":"2026-10-29T13:27:36","modified_gmt":"2026-10-29T13:27:36","slug":"whatsapp-error-130472","status":"publish","type":"post","link":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-error-130472\/","title":{"rendered":"WhatsApp Error 130472: User’s Number Is Part of a Meta Experiment"},"content":{"rendered":"\n

Updated on October 29, 2026<\/em><\/p>\n\n\n\n

WhatsApp error 130472 means your message was not sent because the recipient is part of a Meta experiment. According to the official documentation, WhatsApp withholds marketing template messages from a very small percentage of users unless they have an open customer service window or an open free entry point window with your business. You are not charged, there are no exceptions or opt-outs, and resending returns the same error.<\/p>\n\n\n\n

This article sticks to what Meta documents about 130472, and the second half adds our own operational recommendations for handling the code in your CRM and reports. For the full list of codes, see WhatsApp API error codes<\/a>.<\/p>\n\n\n\n

What Meta says about error 130472<\/h2>\n\n\n\n

In the error codes table<\/a>, 130472 is described as “Message was not sent as part of an experiment”, and the suggested solution points to Meta’s experiments page<\/a>, in the marketing message experiment section.<\/p>\n\n\n\n

Here’s a summary of what that page states:<\/p>\n\n\n\n

Topic<\/th>What the documentation says<\/th><\/tr><\/thead>
Why it exists<\/td>WhatsApp runs experiments to measure how messaging affects user experience and engagement<\/td><\/tr>
Who is affected<\/td>A “very small percentage” of users; the page gives no exact figure<\/td><\/tr>
Which messages<\/td>Marketing template messages only<\/td><\/tr>
When the message goes through<\/td>If the user has an open customer service window or an open free entry point window with the business<\/td><\/tr>
Billing<\/td>WhatsApp does not send the message and does not bill you for it<\/td><\/tr>
Exceptions<\/td>No exceptions or opt-outs are available for these experiments<\/td><\/tr>
Resending<\/td>Attempting to resend results in the same error<\/td><\/tr>
Duration<\/td>The experiment is ongoing, with no fixed end date<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The page does not say who is in the group, how long a user stays in it, or offer an endpoint to check this before sending.<\/p>\n\n\n\n

How 130472 reaches your system<\/h2>\n\n\n\n

The code arrives in the messages<\/code> webhook as a status event with status: \"failed\"<\/code> and code<\/code> 130472 inside the errors<\/code> array. Your send call may have returned success with a wamid<\/code>; the failure shows up later, asynchronously. A simplified example:<\/p>\n\n\n\n

{\n  \"statuses\": [\n    {\n      \"id\": \"wamid.HBgLNTU4NDk5OTk5OTk5...\",\n      \"status\": \"failed\",\n      \"timestamp\": \"1761750000\",\n      \"recipient_id\": \"5584999999999\",\n      \"errors\": [\n        {\n          \"code\": 130472,\n          \"title\": \"Message was not sent as part of an experiment\",\n          \"href\": \"\/documentation\/business-messaging\/whatsapp\/support\/error-codes\"\n        }\n      ]\n    }\n  ]\n}<\/code><\/pre>\n\n\n\n
Branch on code<\/code>, not on the title<\/code> text. If you don’t store status events yet, start with our guide to WhatsApp API message status webhooks<\/a>.<\/p>\n\n\n\n
130472 is not 131049 or 131050<\/h2>\n\n\n\n
All three codes involve marketing templates, so they get mixed up. They need different handling:<\/p>\n\n\n\n
Code<\/th>What it is<\/th>Retry?<\/th><\/tr><\/thead>
130472<\/td>User in a Meta experiment; marketing withheld outside open windows<\/td>No; you get the same error<\/td><\/tr>
131049<\/td>Per-user marketing limit, “to maintain healthy ecosystem engagement”<\/td>Only after at least 24 hours, per Meta<\/td><\/tr>
131050<\/td>The user chose to stop receiving marketing from your business<\/td>No; treat as an opt-out<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
131049 has its own article: WhatsApp error 131049 and the per-user marketing limit<\/a>. The takeaway: if your system lumps all of these together as “marketing failure”, you’ll retry 130472 for nothing and fail to respect the 131050 opt-out.<\/p>\n\n\n\n
Can you work around error 130472?<\/h2>\n\n\n\n
No. Meta says explicitly that there are no exceptions or opt-outs. Rewriting the template, changing the send time or using a different number are not offered as solutions in the documentation.<\/p>\n\n\n\n
What the page does point to is the one official path: reach the user through non-WhatsApp channels and ask them to message you. Once the user starts the conversation, the 24-hour customer service window opens, and inside it the marketing template isn’t withheld by the experiment. According to the pricing page<\/a>, the customer service window opens when the user messages or calls your business. The window rules are covered in the WhatsApp 24-hour customer service window<\/a>, and re-engaging after it closes is covered in error 131047<\/a>.<\/p>\n\n\n\n
The other window Meta mentions is the free entry point window, which opens when a user arrives through a Click to WhatsApp ad and your business replies within the customer service window. Per the pricing page, it can stay open for up to 7 days.<\/p>\n\n\n\n
Cost<\/h2>\n\n\n\n
The experiment documentation is clear: WhatsApp does not send the message and does not bill you for it. That also matches the general rule on the pricing page<\/a>: businesses are only charged when a message is delivered.<\/p>\n\n\n\n
In practice, for a marketing campaign to Brazil (R$ 0.3217, in Brazilian reais, per delivered message since October 1, 2026), contacts that return 130472 don’t add to the bill. If you estimate budget from list size, as shown in how much a WhatsApp campaign costs<\/a>, actual spend will come in slightly below the forecast because of these contacts and other failures.<\/p>\n\n\n\n
How to handle it in your CRM and reports<\/h2>\n\n\n\n
From here on, these are our operational recommendations, not Meta rules. The idea is simple: 130472 says nothing bad about the contact, the number or your campaign. It only says that particular marketing template couldn’t go through at that moment.<\/p>\n\n\n\n
On the contact record<\/h3>\n\n\n\n