To authenticate calls from Rankr to Snapshots API, generate an API key in the GHL developer console and include it in your request headers.
Rankr uses standard OAuth tokens to authorize connections to GHL. Ensure you have the saas/location.read scope enabled when connecting Facebook Audiences.
Available endpoints include: GET /locations to fetch locations to target, POST /audiences to create or update audiences, PATCH /audiences/{id} to apply delta changes. Note: Depending on your plan, additional endpoints may be exposed.
Trigger: When location data changes in GHL, fetch the latest data with GET /locations to refresh Facebook audience segments.
Actions: Map id, name, region, and status to Facebook audience fields and push updates to audiences.
GET /locations
id, name, region, status
Trigger: When a new audience is created or updated in Rankr, push to Facebook via POST /audiences.
Actions: Create or update Facebook audiences using Rankr data; map audienceId, name, and segments.
POST /audiences
audienceId, name, segments
Trigger: Real-time delta from GHL to Facebook audiences as data changes.
Actions: Patch audience records with delta fields; ensure consistency and audit trails.
PATCH /audiences/{id}
id, last_modified, delta
No custom coding required; configuration is done in Rankr’s UI and the GHL connection screen.
Automatic syncing reduces manual updates and human error across campaigns.
Fast deployment to Facebook Ad campaigns with up-to-date audiences across all ad sets.
This glossary explains the core concepts and data flow between GHL, Rankr, and Facebook Ads as you set up the integration.
GHL API: The API that enables programmatic read and write access to GHL resources from external apps.
A defined group of Facebook users targeted by ads based on shared characteristics.
A mechanism that delivers real-time event notifications to your app when data changes.
The process of aligning fields between GHL and Facebook so data maps correctly to audiences.
Automatically refresh Facebook audiences as location data changes in GHL are detected.
Target audiences by location and trigger ads in Facebook when changes occur.
Build a dashboard showing sync status, audience sizes, and performance metrics.
Create or copy API keys in GHL and add them to Rankr’s connection settings.
Map GHL fields to Facebook audience fields in Rankr.
Run end-to-end tests and deploy the workflow to production.
You can sync identifiers like user IDs and location descriptors to Facebook audiences, enabling precise targeting. Ensure you comply with privacy rules and obtain consent where required. Rankr can automate updates so audiences stay fresh without manual work.
No extensive coding is required. The integration uses standard API calls via the GHL API and Rankr UI. Some initial setup is needed to map fields and configure credentials.
Sync frequency is configurable in Rankr, from real-time to daily. Consider Facebook’s pacing recommendations and your ad budget when choosing a cadence.
Permissions include location.read for GHL and the ability to read and write audiences in Facebook. Ensure your app has the necessary scopes approved.
Yes. You can customize field mappings to align with Facebook’s audience fields, including name, id, and segmentation attributes.
If a sync fails, Rankr will retry according to the configured retry policy and log the error. Check the activity feed for details and fix the mapping or credentials.
Sync status is visible in Rankr’s dashboard and in Facebook Ads Manager if the integration is connected. Look for status indicators and recent activity.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
