Facebook Ad Account Restricted: Could My Make.com Automation Be the Cause?


Hi everyone,

I’m hoping to get some clarity on an issue with my Facebook ad account. A week after conducting tests via Make.com (where I was sending automated purchase events), I started running ads. Shortly after launching my ad campaigns, my account was restricted, but I hadn’t sent many events via Make.com since the purchases never actually happened.

Facebook flagged my account for issues with automation, such as rapid activity or behavior that mimics human actions. I’ve attached a screenshot of the restriction message for reference.

Has anyone had a similar experience using Make.com for event tracking on Facebook, or know if testing with automated events (even without real purchases) could have triggered this restriction? I’m not sure if it’s directly related, but any advice on how to prevent this in the future would be really helpful!

Thanks in advance for your insights!

Welcome to the Make community!

Try adding a sleep module with at least 30-60 seconds before each Facebook module to slow down the number of requests to Facebook.

Hope this helps! Let me know if there are any further questions or issues.

@samliew

P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.

Thanks for the suggestion the events are not being sent consistently in a natural environment ie outside of doing tests.

I suspect it’s either due to the tests I did previously or maybe something to do with Make’s configuration for the facebook API module that caused an issue.

They are only guesses though I don’t truly know.