Audience sync automation
Sync CRM lists to Custom Audiences automatically.
Facebook Audiences Connector
Enable your SaaS product to create, update and target Facebook Custom Audiences from inside the app. Build workflows that sync CRM lists, add or remove members on events, and attach audiences to ad targeting for automated campaign workflows.
Event driven updates
Add or remove members when user events occur.
Governed delivery
Expose approved methods as managed MCP tools.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Overview
Integrate your application with Facebook Custom Audiences to create and manage audiences, upload member lists and read audience sizes and related ad-account data. Cyclr connects via Facebook’s OAuth 2.0 flow and uses the Graph/Marketing API to manage Custom Audiences and membership uploads. See the Facebook Audiences API documentation for endpoints and field details. (community.cyclr.com)
PRODUCT USE CASES
Use cases
Quickly build customer-facing automations to sync customer lists, update audiences on user events, generate lookalike sources and pull audience sizing for reporting. Publish them inside your product using Cyclr’s embedded marketplace for multi-tenant delivery.
Sync CRM customers to Custom Audiences
Push email or phone lists from your customer records to create or update a Facebook Custom Audience (create audience, add users). (github.com)
Update audiences on user events
On purchase, subscription or churn events add or remove users from a Custom Audience to keep targeting accurate (add_users, remove_users). (github.com)
Attach audiences to ad targeting
Automate attaching a Custom Audience to ad sets or campaign targeting to enforce campaign logic from your app (ad set targeting APIs). (geekblog.net)
ORCHESTRATION
How Facebook Audiences works with Cyclr
Cyclr sits between your SaaS product and Facebook Audiences to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
Facebook Audiences
Facebook Audiences processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore Facebook Audiences methods you can orchestrate through Cyclr.
Ad Accounts1
Get My Ad Accounts
ActionGets the advertising accounts to which you have access.
Members3
Add Email Audience Member
ActionAdd a member using email address match.
Add Audience MultiKey Members
ActionAdd users using multi-key matches.
Remove Audience Members
ActionDelete audience members.
Audience6
Delete Audience
ActionDeletes an audience.
Get Updated (Metadata) Audiences List
ActionGets a list of audiences for the ad account where audience metadata has been updated since the last cycle run.
Get Audience List
ActionGets a list of audiences for the ad account.
Create Audience
ActionCreate a audience.
Get Audience
ActionGets audience details.
Get Updated Audiences List
ActionGets a list of audiences for the ad account where members have been updated since the last cycle run.
TECHNICAL DETAILS
Facebook Audiences integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing Facebook Audiences integrations in Cyclr.
API and authentication
- API host
https://graph.facebook.com- Authentication
- OAuth 2.0
- Credentials
Client ID (App ID) and Client Secret entered in Cyclr Partner Console.
- Method categories
Audience CRUD; member uploads; ad-account reads and insights.
Pagination and rate limits
Pagination
Cursor-based pagination: Graph API returns paging.next/previous URLs and after/before cursors for list endpoints. (github.com)
Rate limits
Marketing API uses Business Use Case (BUC) rate limits scoped per ad account; responses include rate-use headers like X-Business-Use-Case-Usage. (github.com)
IMPLEMENTATION
Authentication at a glance
Uses OAuth 2.0 via a Facebook App; Cyclr stores the App ID and App Secret to perform the OAuth flow for partner installs. (community.cyclr.com)
- Authentication method
- OAuth 2.0
- Credential required
Client ID (App ID) and Client Secret entered in Cyclr Partner Console.
Before you begin:
View setup guideFacebook App Review and Business verification required for production access.
COMMON QUESTIONS
Frequently asked questions
It can create and manage Custom Audiences, upload or remove audience members, read audience sizes and trigger audience updates from app events. This uses the Marketing Graph API endpoints for audiences and member uploads. (github.com)
OAuth 2.0. You register a Facebook App, add the Marketing API product, then supply App ID and App Secret in Cyclr; Cyclr uses OAuth to obtain access tokens. App Review and business verification are required for production. (community.cyclr.com)
Yes. Cyclr supports multi-tenant flows where each customer authorizes their Facebook ad account via OAuth, so your product can manage separate audiences per customer while using a central partner app. (community.cyclr.com)
Yes. You can publish approved audience actions (create audience, add users, list audiences) as governed MCP tools in Cyclr for controlled, audited use inside your product. (community.cyclr.com)
KEEP EXPLORING
Related resources and connectors
Documentation
What is iPaaS?
Read more →ProductHow to develop an API – Best Practices to Follow from Cyclr Developers
Read more →ProductMCP PaaS
Read more →Related connectorFacebook Conversions
Related Social Media connector for customer-facing integration workflows.
Related connectorFacebook Insights
Related Social Media connector for customer-facing integration workflows.
Related connectorFacebook Marketing API
Related Social Media connector for customer-facing integration workflows.