Authenticate with the Snapshots API using a secure API key or OAuth 2.0 flow. The integration requires saas/location.read scope to fetch location data for audience targeting.
Authorize the Zapier App Connector (APPNAME) to access Snapshots API data via OAuth 2.0, and ensure tokens are stored securely for ongoing automations.
GET /locations — Retrieve the list of locations to target LinkedIn Ads audiences.
Triggered when a new location or update is available, pulling location_id, location_name, and country_code for audience segmentation.
Actions: fetch /locations, map fields to LinkedIn audience attributes, update ad targeting in LinkedIn Ads.
GET /locations
location_id, location_name, country_code
Triggered when location data changes, refreshing LinkedIn audiences with the latest locations.
Actions: enqueue data sync, push updated location data to LinkedIn Ads audiences.
GET /locations
location_id, updated_at
Triggered when a location tag or region changes, enabling dynamic ad content.
Actions: map location fields to dynamic LinkedIn ad content, adjust campaigns automatically.
GET /locations
location_id, region, feature_flags
Build powerful automations without writing a line of code.
Visual data mapping between Snapshots API and LinkedIn Ads in seconds.
Faster go-to-market with reusable templates for campaigns.
Definitions and concepts to help you implement the integration, including endpoints, triggers, actions, and data fields.
A specific URL path and HTTP method that performs an operation on the Snapshots API, such as GET /locations.
An event in Zapier that starts a workflow, such as new or updated location data.
An operation performed by the Zapier app, such as updating a LinkedIn Ads audience.
The process of aligning fields from Snapshots API to the corresponding fields in LinkedIn Ads.
Set up a recurring, event-driven sync that updates LinkedIn audience segments whenever location data changes in Snapshots API.
Convert location data into region-aware ad content for multi-market campaigns with automated field mapping.
Aggregate location-driven KPI metrics and push alerts to your team via Slack or email for rapid optimization.
Begin by authorizing the Zapier App Connector to access the Snapshots API using OAuth 2.0.
Select GET /locations as the primary endpoint and set up triggers for new or updated location data.
Map location_id, location_name, and country_code to LinkedIn Ads fields and run end-to-end tests.
No extensive coding is required. The Zapier App Connector provides a no-code bridge that connects Snapshots API to LinkedIn Ads. Use triggers, actions, and field mappings to automate data flow. If you have basic API familiarity, you can set up the workflow in minutes. For advanced users, you can customize signals and conditions within Zapier’s editor.
The primary endpoint used is GET /locations to fetch location data for audience targeting. You can expand later to additional endpoints if needed, but this page focuses on the location data flow to feed LinkedIn Ads audiences.
Data is transmitted over HTTPS with OAuth 2.0 tokens. Access is scoped to saas/location.read, ensuring read-only location data for audience targeting. Regular token rotation and secure storage are standard practices.
Yes. You can map custom fields from Snapshots API to corresponding LinkedIn Ads fields using Zapier’s data mapper. This enables personalized targeting and richer audience definitions without code.
Triggers are fired when location data is created or updated in Snapshots API, or when a scheduled sync occurs. This ensures LinkedIn audiences stay aligned with current data.
You can view logs and run history within both Snapshots API access and Zapier task history. Zapier provides detailed run results, including errors and mapping details, to help you diagnose issues quickly.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
