Meta Dev App errors

Joined
Jan 29, 2026
Messages
2
Reaction score
0
Hi! I'm running into a new issue and was hoping to get your opinion. I use a script to extract spend data from my Meta ad accounts. The script relies on the Ad Account ID and an access token generated through a Meta Developer app, which connects the ad accounts to a Google Sheet. Recently, however, the Developer app has been throwing more and more errors, making the script unreliable. Is there an alternative way to automatically extract ad spend without relying on a Meta Developer app?
Separately, I use cloaking with Keitaro. My filters are configured as follows:
  • Traffic is not from Facebook/Instagram.
  • Device is not a computer, phone, or tablet.
  • [S2] Campaign ID os @empty, {{campiagn.id}}
  • A web proxy is detected.
  • Country is not the selected target country.
  • Visitor is identified as a bot.
My landing pages are built on WordPress.

Do you think the increasing number of account issues is related to the cloaking setup, or is Meta simply getting better at detecting these types of configurations?
 
those dev app errors are almost always token related, meta shortened token lifespans a lot recently so scripts break more often now.
cloaking setup looks solid, more likely meta's just getting better at pattern detection on the account/campaign behavior side not ur keitaro filters specifically.
 
Back
Top