New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to get 'X-FB-Ads-Insights-Throttle' header from response? #48
Comments
Check the |
Joe thanks a lot. I'm also trying to handle an ad account being limited or app being limited and catching it with a begin -> rescue but the last_api_response can't be found in the rescue. Maybe I should just make sure it never happens as opposed to trying to handle when it does |
I'm already performing some sort of "ping" to the ad account before performing anything so I might be good but you can never be too safe. There's always the scenario that when you ping the adaccount everything is fine but halfway through processing they reach their limit you know |
This allows access to the headers of the request that caused the error:
produces this:
|
That helps tremendously thank you so much Joe! One last question. Do you know if there's an option to not allow users to edit campaigns made through the API in their ads managers? Or is that impossible. |
You are welcome! Unfortunately, I don't know if there is a way to block users from editing API created campaigns with Ads Manager. Sorry! |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. Thank you for your contributions. |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information. |
Trying to create a scheduled job to fetch insights from customer ad accounts but I need to constantly check the 'X-FB-Ads-Insights-Throttle' header in order to make sure Facebook doesn't limit me.
How can I check this header when calling the insights calls using the library?
The text was updated successfully, but these errors were encountered: