Follow our Webhooks Getting Started guide to create your endpoint and configure your Webhooks. When you configure your webhooks, make sure to choose Ad Account.
Currently, you can get real-time notifications for ad object status changes for WITH_ISSUES and IN_PROCESS. Subscribe to one or more fields below:
Field
Description
with_issues_ad_objects
Notifies you when a campaign, ad set or ad under the ad account receives the WITH_ISSUES status.
in_process_ad_objects
Notifies you when a campaign, ad set, or ad exits the IN_PROCESS status. See post processing for more information.
ad_recommendations
Notifies you when ad recommendations generated for your ads.
creative_fatigue
Notifies you when your ad enters or exits fatigue. Provides more granular information with different fatigue levels such as Low, Medium, and High.
product_set_issue
Notifies you when a product set encounters issues that affect your ads.
Subscribe Your App
You need to subscribe your app to webhook notifications for your ad account. You app should have edit permission to the ad account to complete this step. The app should also have ads_management permission.
To subscribe your app, have your app send a POST request subscribed_apps for the ad account:
curl -i -X POST \
-d "access_token=<ACCESS_TOKEN>" \
"https://graph.facebook.com/<VERSION>/act_<AD_ACCOUNT_ID>/subscribed_apps?app_id=<APP_ID>"
On success, you see this response:
{"success": "true"}
To see which app's are subscribed for your ad account has subscribed, send a GET request:
curl -i -X GET \
-d "access_token=<ACCESS_TOKEN>" \
"https://graph.facebook.com/<VERSION>/act_<AD_ACCOUNT_ID>/subscribed_apps"
Replace the me?fields=id,name query with act_AD_ACCOUNT_ID/subscribed_apps. It will subscribe the app you use to send the POST request in Graph Explorer.
Or you can subscribe a different app by specifying subscribed_apps as an input parameter with the app id.
The app must have permission to edit the ad account in order to subscribe.
