Meta Ads in BeKnow
Manual daily account-level impressions, clicks, spend and actions using an ads_read token.
What this integration does
Manual daily account-level impressions, clicks, spend and actions using an ads_read token. Source action types and attribution remain distinct; there is no automatic cross-platform deduplication. Initial implementation: validation with the intended real account is still required.
Manual import · Initial version
Check the source, collection date and scope before using a result.
Data BeKnow can use
- Manual daily account-level impressions, clicks, spend and actions using an ads_read token.
Where BeKnow uses it
- Inspect imported records in the connection’s Data view.
- Read records and import history through authorised MCP operations.
How to connect
- 1
Open the intended workspace’s integration settings.
- 2
Select Meta Ads and provide the required authorisation.
- 3
Start the manual import and inspect its completion, dates and records.
What you need
Ad account ID and an authorised access token with ads_read permission.
Who pays for usage
Memory and these reads do not require a BeKnow model key. Your external account, API access and any AI client follow their own service terms.
Frequently asked questions
Current scope?
Manual daily account-level impressions, clicks, spend and actions using an ads_read token. Source action types and attribution remain distinct; there is no automatic cross-platform deduplication. Initial implementation: validation with the intended real account is still required.
Do I need an AI subscription?
Project memory and data imports do not require an AI model key. A compatible external AI client may have its own costs. BYOK applies only to available functions that actually call an external provider.