Move Apple Ads data anywhere it matters.

Move Apple Ads data into your warehouse, lake or AI app.

Sync Apple Ads free Read the docs

Source

Apple Ads

Snowflake
BigQuery
Postgres
Databricks
Claude

Destinations: 50+
Standard support: 1.1.21

Overview

What is the Airbyte Apple Ads connector?

The Airbyte Apple Ads connector extracts data from Apple Ads and loads it into 50+ destinations such as Snowflake, BigQuery, Databricks or Postgres, with full refresh and incremental sync. It publishes tables and events you can select per connection.

01
Sync to your warehouse
Land Apple Ads data in 50+ destinations on a schedule you control.
02
Incremental syncs
Pull only the records that changed since the last run instead of reloading everything.
03
One authorization
Authenticate Apple Ads once and Airbyte keeps every scheduled sync running on it.
04
Cloud or self-hosted
Run the Apple Ads connector on Cloud, OSS, Hybrid.

Setup

Live in five steps

Sign in to Apple Ads as an account administrator, select the account from the Users menu, and go to Account Settings → User Management.
Click Invite Users. In User Access and Role, select an API role, such as API Account Manager or API Account Read Only, and send the invite. The invited user activates the account from the invitation email.
As the API user, generate a private key and extract its public key: bash openssl ecparam -genkey -name prime256v1 -noout -out private-key.pem openssl ec -in private-key.pem -pubout -out public-key.pem
In Apple Ads, go to Account Settings → API, paste the contents of public-key.pem into Public Key, and click Save. Apple then shows your clientId, teamId, and keyId.
Create the client secret: a JWT signed with private-key.pem using the ES256 algorithm, with these values: - Header: alg is ES256 and kid is your keyId. - Payload: sub is your clientId, iss is your teamId, aud is https://appleid.apple.com, iat is the current UNIX timestamp, and exp is a UNIX timestamp less than 180 days after iat. The encoded JWT is the value for Client Secret in Airbyte. Keep the private key secure; you need it every time you create a new client secret.

Configuration fields

Apple Ads configuration fields
Field	Type	Description
client_id*	string	A user identifier for the token request. See here
client_secret*	string	A string that authenticates the user’s setup request. See here
org_id*	integer	The identifier of the organization that owns the campaign. Your Org Id is the same as your account in the Apple Search Ads UI.
start_date*	string	Start getting data from that date.
timezone*	string	The timezone for the reporting data. Use 'ORTZ' for Organization Time Zone or 'UTC' for Coordinated Universal Time. Default is UTC.
token_refresh_endpoint*	string	Token Refresh Endpoint. You should override the default value in scenarios where it's required to proxy requests to Apple's token endpoint
backoff_factor	integer	This factor factor determines the delay increase factor between retryable failures. Valid values are integers between 1 and 20.
end_date	string	Data is retrieved until that date (included)

Hybrid deployment

Sovereign by architecture, not by policy.

The data plane runs in your environment. Records, credentials and keys stay with you; the control plane only receives configuration and job metadata.

Cloud
OSS
Hybrid

Your environment

DataConnectorsCredentialsKeys

↕ metadata only

Airbyte control plane

OrchestrationMonitoringUI

FAQ

Apple Ads connector questions

What data can I sync from Apple Ads with Airbyte?

The Apple Ads connector syncs the tables and events published in Airbyte docs.

Does the Apple Ads connector support incremental sync?

Yes. The Apple Ads connector supports incremental sync on selected streams, and full refresh on every stream.

Where can I run the Apple Ads connector?

Run the Apple Ads connector on Cloud, OSS, Hybrid. Hybrid deployments keep the data plane in your environment while the control plane orchestrates syncs.

Didn't find your answer? Talk to sales