Linking Naver Ads as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Contents
The Naver Ads connector syncs your Naver Search Ads campaigns, ad groups, ads, keywords, and daily performance into the PostHog data warehouse. Use it to compare search ad spend and clicks with what those visitors do in your product.
Prerequisites
You need access to a Naver Search Ads account in Search Ad Manager, and permission to create an API license for it.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
When linking Naver Ads, you need:
- API license – the access license shown for your API license in API Manager
- Secret key – the secret key of your API license
- Customer ID – the numeric ID of the ad account
To get these:
- Log in to Search Ad Manager.
- Go to Tools > API Manager.
- Create an API license, or open an existing one.
- Copy the API license, secret key, and customer ID into PostHog.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
campaigns, adgroups, ads, and keywords use full refresh. Each sync replaces the table.
campaign_stats, adgroup_stats, and keyword_stats hold one row per entity per day, in Korea Standard Time. They support incremental sync on date. Each incremental sync reads the last two days again, because Naver can update metrics for up to 48 hours.
The first sync of a stats table reads 365 days for campaign and ad group stats, and 90 days for keyword stats. Naver keeps stats for up to two years.
Configuration
| Option | Type | Required |
|---|---|---|
API license | password | Yes |
Secret key | password | Yes |
Customer ID | text | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
campaigns | Search ad campaigns in the account. | Full refresh | — | — |
adgroups | Ad groups, each belonging to one campaign. | Full refresh | — | — |
ads | Ads, each belonging to one ad group. | Full refresh | — | — |
keywords | Keywords, each belonging to one ad group. | Full refresh | — | — |
campaign_stats | Daily performance metrics per campaign. | Incremental, Full refresh | date | — |
adgroup_stats | Daily performance metrics per ad group. | Incremental, Full refresh | date | — |
keyword_stats | Daily performance metrics per keyword. | Incremental, Full refresh | date | — |
Troubleshooting
- Invalid credentials – check that the API license, secret key, and customer ID all come from the same API license in Tools > API Manager, then reconnect the source.
- Slow keyword stats syncs – keyword stats need one request per 100 keywords per day. Accounts with many keywords take longer to sync this table.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.