Facebook Custom Audiences Destination
Overview
The Facebook Custom Audiences Destination sends audience segments from Sourcesible directly to your Facebook Custom Audiences account, enabling ad suppression, retargeting, acquisition via lookalikes, and more. Once connected, this Destination becomes available for use with Audiences and other activation features in Sourcesible.
Before setting up this Destination, ensure you have an active Facebook Business Account and a Facebook Ad Account with the Custom Audiences feature enabled.
2. Credential & Permission Setup
This Destination uses OAuth — no manual API keys or credentials are required. Sourcesible will request limited access to your Facebook Custom Audiences account during setup. Your credentials are encrypted, and authorization can be revoked at any time from Facebook's settings.
Ensure the Facebook account you use to authenticate has:
- Access to a Facebook Business Account
- Admin or Advertiser role on the target Facebook Ad Account
- The Custom Audiences feature enabled on that Ad Account
If your Facebook Ad Account has Custom Audience terms of service pending acceptance, the connection will succeed but audience syncs will fail until the terms are accepted in Meta Business Manager.
3. Connection Configuration (Inside Sourcesible)
3.1 Open the Destinations Catalog
- In the left navigation, click Destinations.
- Click Add Destination in the top right corner.
- From the Destinations List, click the Facebook Custom Audiences card.
3.2 Review Setup Requirements
- On the Facebook Custom Audiences detail page, review the Set up requirements:
- Facebook Business Account
- Facebook Ad Account
- Click Add Destination to begin the setup wizard.
3.3 Authorize Facebook Connection (Step 1 — Connect)
- On the Connect to Facebook Custom Audiences screen, click Log in to Facebook Custom Audiences.
- A Facebook OAuth dialog will open. If you are already logged in, Facebook will ask you to confirm continuing as your current account — click Continue. If you need to use a different account, click Log in to another account.
- Review the permissions Sourcesible is requesting and click Continue to authorize.
- You will be redirected back to Sourcesible automatically. The connection indicator will show Authorization Successful — your Facebook Custom Audiences account is now connected to Sourcesible.
Do not close the browser tab or the Facebook dialog during the OAuth flow. Closing it before the redirect completes will cancel the authentication and you will need to restart from Step 6.
3.4 Set Up the Destination (Step 2 — Set up Destination)
- In the Destination Name field, enter a name for this connection (e.g., Facebook Custom Audiences). You can change this at any time under Settings.
- Optionally, enter a Destination Description to help your team identify this connection.
- In the Facebook Ad Account dropdown, select the Ad Account you want Sourcesible to sync audiences to.
- Click Save Destination.
Sourcesible will return you to the Destinations page, where the new connection will appear with a Connected status and a confirmation banner: Your destination has been connected successfully.
4. Test Your Connection
After saving, Sourcesible confirms the connection is active by displaying a Connected status on the Destinations page. The following are validated during setup:
- ✅ OAuth token is valid and the Facebook account is authorized
- ✅ The selected Facebook Ad Account is accessible by the authenticated user
- ✅ Sourcesible can communicate with the Facebook Custom Audiences API
The Sync column on the Destinations page will show - until the first audience sync is triggered. The Last Update timestamp reflects when the connection was established.
5. Next Steps
With your Facebook Custom Audiences Destination connected, you can:
- Sync an Audience to Facebook Custom Audiences — Push customer segments for retargeting, suppression, or lookalike campaigns
- Set Sync Frequency — Control how often Sourcesible updates the audience in Facebook
- Monitor Destination Health — View sync logs, error rates, and delivery status from the Destinations page
6. Tips and Troubleshooting
OAuth Authorization Fails or Redirects to an Error Page
Symptom: Clicking Log in to Facebook Custom Audiences results in an error page or the OAuth dialog closes without returning to Sourcesible.
Cause: This can happen if third-party cookies are blocked in your browser, or if a popup blocker prevents the Facebook dialog from opening correctly.
Fix: Ensure that your browser allows popups from cdp-sit-app.predictive.dev and that third-party cookies are not blocked for facebook.com. Try disabling any browser extensions that may interfere, then restart the OAuth flow from Step 6.
Facebook Ad Account Not Appearing in the Dropdown
Symptom: After authorization, the Facebook Ad Account dropdown is empty or does not show the expected Ad Account.
Cause: The Facebook account used to authenticate does not have Admin or Advertiser access to the target Ad Account, or the Ad Account is restricted by Meta.
Fix:
- Log in to Meta Business Manager.
- Navigate to Business Settings → Ad Accounts and confirm the authenticated user has the correct role.
- Return to Sourcesible, click Back to return to Step 1, and re-authenticate with the correct Facebook account.
Audience Syncs Fail After Successful Connection
Symptom: The Destination shows Connected status but audience syncs fail with a policy or terms-related error.
Cause: The Facebook Ad Account has pending Custom Audiences terms of service that have not yet been accepted.
Fix:
- Log in to Meta Business Manager.
- Navigate to Business Settings → Data Sources → Custom Audiences.
- Accept the Custom Audiences terms of service for the relevant Ad Account.
- Return to Sourcesible and re-trigger the audience sync.
OAuth Token Expired
Symptom: A previously connected Destination shows a failed or disconnected status.
Cause: Facebook OAuth tokens expire or are invalidated when the user changes their Facebook password or revokes Sourcesible's access.
Fix:
- Navigate to Destinations and open the affected Destination.
- Click Reconnect and complete the OAuth flow again.
Use a shared team or service Facebook account for this Destination where possible. Tokens tied to personal accounts are invalidated if the account owner changes their password or revokes app permissions.