Ads + APIs
DJINN + Meta
Campaign performance and spend pulled into the same place as everything else, so ad results sit next to the work that caused them.
How it connects
Spend against outcome
Ad platforms report clicks. What matters is which campaign produced a customer, which needs the CRM and the ad account read together.
Budget changes stay human
Reading performance is automatic. Moving money is not.
Connector spec
- Auth
- oauth2 · meta_v1
- Host
- https://graph.facebook.com
Scopes requested
GET v21.0/${source.id}/posts
Emits post · incremental on created_time · cursor pagination
Declared boundary: anyone in the workspace
This spec parses and validates, and it has not been run against a live Meta account. Sigil fetches and paginates today; it does not yet apply the mapping or enforce the boundary shown here. Both are declared and checked for shape, not executed.
Documents
Meta setup and reference.
Setup steps, scopes, and the policy boundaries that govern this connector. Sent by email — leave an address and we send them manually, same as the handbook.
- SetupAd account access and scopes
- ReferenceAttribution reporting
Want Meta wired into your own company brain?