AdSkull
URL to AI UGCCampaign AutomationAI CopilotMeta Ads AutomationTikTok Ads AutomationSnapchat Ads AutomationAI Video StudioAI Image StudioFree ToolsFREEPricingFor AgenciesExamples GalleryAffiliate ProgramAPI DocsContact
Get started free
Meta / Facebook APIError 1487694

Meta API Error 1487694 — Targeting Category Deprecated

Meta API error 1487694 can appear when an ad set uses a deprecated targeting category. Learn how to replace removed interests and behaviors with Targeting Search.

Quick Answer

Meta API error 1487694 can mean one of your targeting categories, interests, or behavior IDs is no longer valid. Fix it by removing deprecated targeting IDs, calling Meta Targeting Search for current replacements, and rebuilding the ad set with valid flexible_spec or targeting fields before publishing.

What Causes Meta / Facebook Error 1487694?

Meta regularly deprecates interests, behaviors, partner categories, and detailed targeting options. Saved templates and old automation scripts often keep stale targeting IDs. When an ad set payload includes a retired targeting object, the Marketing API can reject the publish request even though the same template worked previously.

  • 1Saved campaign template includes a removed interest or behavior ID
  • 2A detailed targeting category was deprecated in a recent Meta API version
  • 3Your automation copied targeting from an old ad set without revalidating it
  • 4A partner category or demographic segment is no longer available in the target country
  • 5The payload mixes legacy targeting fields with newer flexible_spec structures

How to Fix Meta / Facebook Error 1487694

  1. 1Log the full targeting payload sent with the failed ad set request.
  2. 2Remove each interest, behavior, or demographic targeting ID and test until the invalid object is isolated.
  3. 3Call Meta Targeting Search with the original category name to find a current replacement ID.
  4. 4Rebuild the ad set targeting with valid flexible_spec fields and current targeting IDs.
  5. 5Version campaign templates so old deprecated IDs are not reused silently.
  6. 6Run a preflight targeting validation before every bulk launch.

Official Meta / Facebook Documentation

https://developers.facebook.com/docs/marketing-api/error-reference

↗
Never Deal With This Again

AdSkull Handles Meta / Facebook API Errors Automatically

Stop manually debugging API errors. AdSkull monitors your Meta / Facebook campaigns 24/7, detects authentication failures and permission issues, and surfaces clear actionable fixes — or handles them automatically when possible.

✓Automatic token refresh before expiry
✓Real-time permission alerts
✓Smart retry with exponential backoff
✓Unified dashboard for all platforms
✓Plain-English error explanations
✓One-click reconnect for auth issues
Fix This For Good — Free TrialView Integration Docs

Other Meta / Facebook API Errors

190

Invalid OAuth Access Token

Meta API error 190 means your access token is invalid, expired, or has been revoked. Step-by-step guide to re-generating a valid Meta user or system access token.

200

Permission Error

Meta API error 200 means the app lacks permission for the requested operation. Learn which permissions are needed and how to request the correct scopes.

80004

Too Many API Calls

Meta API error 80004 means you have exceeded the rate limit. Learn how Meta rate limits work and how to implement proper throttling and backoff to fix this.

100

Invalid Parameter

Meta API error 100 means one or more parameters in your API request are invalid. Learn how to identify the invalid parameter and fix your request.

1870034

Custom Audience Terms Not Accepted

Meta API error 1870034 blocks audience creation when Custom Audience Terms have not been accepted. Learn the exact Business Manager fix before relaunching campaigns.

← All API Error Guides