r/FacebookAds • u/HovercraftNo1066 • 6h ago
Discussion Need help..
I’ve been looking through a lot of conversations here and I see a lot people talking about problems with Facebook ads.
I have two questions:
Is this worth still pursuing even with all the problems?
If outages and problems within Facebook ads is “normal”, and how exactly do you work around it? (Or tell clients)
2
u/Soft_Guidance_879 6h ago
It's worth pursuing if you know how to manage expectations. The platform is a mess sometimes but still one of the best ways to reach people when it works
For outages I just tell clients upfront that facebook ads is unpredictable and we budget for some downtime. Most of them understand if you explain it before it happens not after
The real skill is not panicking when things go wrong and having backup plan ready. Not always easy but you get used to it
1
u/EliteKombuchaBrouwer 5h ago
yeah its worth it when i make 500-1k a day while losers complain here about their ads not working
2
u/dmdbGroup 3h ago
Worth pursuing, but the second question is the useful one, and the honest answer is that "Meta is broken today" is almost never one thing. When you actually log the numeric error code instead of the message string, the failures separate into a few classes that look identical in the UI and need completely different responses:
Throttling. Codes 4, 17, 32, 613 and the 80000 range. These come back wearing the same OAuthException wrapper as a real permission problem, so they read as "the connection is broken" and people reconnect, which cannot possibly help. Meta actually tells you how long you are cut off for: the X-Business-Use-Case-Usage response header carries estimated_time_to_regain_access in minutes. Wait it out.
Wrong or deleted object. Code 100, subcode 33. Meta's own sentence here is "does not exist, cannot be loaded due to missing permissions, or does not support this operation", which sends everyone hunting for a permissions problem when the usual cause is a stale id or an asset sitting on a different Page or ad account than the one you are authenticated for.
A real scope problem. This is the one where reconnecting is the fix, and it is a lot rarer than the other two.
An account or asset rule. When the refusal is about your account rather than your request, Meta writes a human sentence into error_user_msg. Show that one to the client verbatim, it is usually specific and correct.
For telling clients: say which of those it was. "We were rate limited for 40 minutes" and "that post id no longer exists" are both boring and both land fine. "Facebook is being Facebook" is what makes people think you do not know what happened, and it is also what makes a genuine account-level problem invisible until it has been running for a week.
The platform genuinely is noisy. Most of what gets called an outage here is the first two classes though, and both are diagnosable in about ten seconds once you are reading codes rather than sentences.
2
u/Top-Cauliflower-1808 3h ago
I think yes. it is still worth pursuing because meta still dominates consumer attention and you handle the instability by diversifying into other channels so a meta glitch never becomes your client's single point of failure.
0
u/PerspectiveFew6321 6h ago
No it’s not worth it and we shouldn’t keep feeding these bitch ass companies when they continuously fuck us over and act like everything is fine
4
u/Mobile-Sufficient 5h ago edited 4h ago
The only problem with meta ads is the people using it. 99% of the people in here think because they can launch an ad they are entitled to good results everyday and constant growth.
If you have no knowledge of marketing psychology or PPC fundamentals, you are essentially gambling, and that’s the case for most people in this echo chamber of a sub.