Marketing · Source connector
Naver Ads ELT Connector
Extract brings Naver Ads marketing data into data warehouses and databases for analysis with the rest of your business data. Teams use it to analyze campaign, creative, placement, spend, and revenue performance at a granular level. Flexible scheduling keeps reporting current for routine analysis and time-sensitive decisions.
View setup guide
Use cases
What teams use this connector for
Granular campaign optimization
Analyze Naver Ads campaign, creative, placement, geo, device, spend, and revenue detail to find opportunities to improve performance.
Direct-network reporting
Compare granular Naver Ads data with standard MMP and cost-aggregation reporting to work with dimensions those tools do not make available.
Spend and revenue reconciliation
Reconcile Naver Ads spend and revenue with finance, attribution, and internal performance data to investigate discrepancies.
Flexible performance monitoring
Refresh Naver Ads pacing, anomaly, and performance views every 15 minutes, hourly, daily, or on a custom schedule.
Warehouse and database analysis
Use Extract to make Naver Ads marketing data available in data warehouses and databases such as Snowflake, BigQuery, Redshift, and PostgreSQL for governed analysis.
Audience and campaign activation
Combine Naver Ads performance data with approved customer models, then use Extract Reverse ETL to activate audience or campaign updates downstream.
Connector data
Available streams
| Stream | Description | Sync mode |
|---|---|---|
ad | Fields include customer_id, ad, ad_attr, edit_tm. | Incremental |
ad_account | Fields include customer_id, ad_account_no, created_at, favorite. | Full refresh |
ad_asset_link_master_report | Fields include customer_id, asset_link_id, asset_id, ncc_ad_id. | Full refresh |
ad_conversion_detail_report | Fields include customer_id, stat_dt, campaign_id, adgroup_id. | Incremental |
ad_conversion_report | Fields include customer_id, stat_dt, campaign_id, adgroup_id. | Incremental |
ad_detail_report | Fields include customer_id, stat_dt, campaign_id, adgroup_id. | Incremental |
ad_extension | Fields include customer_id, ncc_ad_extension_id, type, owner_id. | Incremental |
ad_extension_conversion_report | Fields include customer_id, stat_dt, campaign_id, adgroup_id. | Incremental |
ad_extension_master_report | Fields include customer_id, ad_extension_id, extension_tp, owner_id. | Full refresh |
ad_extension_performance_report | Fields include customer_id, stat_dt, campaign_id, adgroup_id. | Incremental |
ad_group | Fields include customer_id, ad_rolling_type, adgroup_attr_json, adgroup_type. | Incremental |
ad_group_budget_master_report | Fields include customer_id, ncc_adgroup_id, use_daily_budget, daily_budget. | Full refresh |
ad_group_master_report | Fields include customer_id, ncc_adgroup_id, ncc_campaign_id, name. | Full refresh |
ad_group_stats_daily | Fields include customer_id, ncc_adgroup_id, stat_dt, imp_cnt. | Incremental |
ad_keyword | Fields include customer_id, ad_relevance_score, attr, bid_amt. | Incremental |
ad_master_report | Fields include customer_id, ncc_adgroup_id, ncc_ad_id, inspect_status. | Full refresh |
ad_performance_report | Fields include customer_id, stat_dt, campaign_id, adgroup_id. | Incremental |
ad_quality_index_master_report | Fields include customer_id, ncc_ad_id, quality_index, _singular_extract_timestamp. | Full refresh |
asset_master_report | Fields include customer_id, asset_id, asset_tp, inspect_status. | Full refresh |
biz_master_report | Fields include id, business_name, super_business_id, level. | Full refresh |
bizmoney | Fields include customer_id, bizmoney, budget_lock, refund_lock. | Full refresh |
bizmoney_charge_history | Fields include customer_id, display_cd, display_name, new_non_refundable_amt. | Incremental |
bizmoney_daily_status | Fields include customer_id, add_non_refundable_amt, add_refundable_amt, non_refundable_amt. | Incremental |
bizmoney_exhaust_history | Fields include customer_id, activity_cd, campaign_tp, prod_info_cd. | Incremental |
brand_banner_ad_master_report | Fields include customer_id, ncc_adgroup_id, ncc_ad_id, inspect_status. | Full refresh |
brand_new_contract | Fields include customer_id, adgroup_name, adgroup_template_name, bid_amt. | Full refresh |
brand_thumbnail_ad_master_report | Fields include customer_id, ncc_adgroup_id, ncc_ad_id, inspect_status. | Full refresh |
business_channel | Fields include customer_id, adult_status, black_status, business_info. | Full refresh |
business_channel_master_report | Fields include customer_id, name, business_channel_id, business_channel_tp. | Full refresh |
campaign | Fields include customer_id, campaign_tp, daily_budget, delivery_method. | Incremental |
campaign_budget_master_report | Fields include customer_id, ncc_campaign_id, use_daily_budget, daily_budget. | Full refresh |
campaign_master_report | Fields include customer_id, ncc_campaign_id, name, campaign_tp. | Full refresh |
campaign_stats_daily | Fields include customer_id, ncc_campaign_id, stat_dt, imp_cnt. | Incremental |
catalog_ad_master_report | Fields include customer_id, ncc_adgroup_id, ncc_ad_id, inspect_status. | Full refresh |
contents_ad_master_report | Fields include customer_id, ncc_adgroup_id, ncc_ad_id, inspect_status. | Full refresh |
criterion | Fields include customer_id, bid_weight, code_name, del_flag. | Full refresh |
criterion_conversion_report | Fields include customer_id, stat_dt, criterion_id, pc_mobile_type. | Incremental |
criterion_master_report | Fields include customer_id, dictionary_code, criterion_tp, owner_id. | Full refresh |
criterion_performance_report | Fields include customer_id, stat_dt, criterion_id, pc_mobile_type. | Incremental |
hospital_ad_master_report | Fields include customer_id, ncc_adgroup_id, ncc_ad_id, inspect_status. | Full refresh |
ip_exclusion | Fields include customer_id, filter_ip, ip_filter_id, login_id. | Full refresh |
keyword_master_report | Fields include customer_id, ncc_keyword_id, ncc_adgroup_id, keyword. | Full refresh |
label | Fields include customer_id, color, ncc_label_id, name. | Full refresh |
label_master_report | Fields include customer_id, label_id, name, reg_tm. | Full refresh |
label_ref_master_report | Fields include customer_id, label_id, reference_id, reg_tm. | Full refresh |
manager_account | Fields include customer_id, naver_id, role_name, created_at. | Full refresh |
media_master_report | Fields include media_tp, id, name, url. | Full refresh |
place_ad_master_report | Fields include customer_id, ncc_adgroup_id, ncc_ad_id, inspect_status. | Full refresh |
product_group | Fields include customer_id, attr_json, brand_name, brand_no. | Full refresh |
product_group_master_report | Fields include customer_id, product_group_id, business_channel_id, name. | Full refresh |
product_group_rel_master_report | Fields include customer_id, product_group_rel_id, product_group_id, ncc_adgroup_id. | Full refresh |
quality_index_master_report | Fields include customer_id, ncc_adgroup_id, ncc_keyword_id, keyword. | Full refresh |
rsa_ad_master_report | Fields include customer_id, ncc_adgroup_id, ncc_ad_id, inspect_status. | Full refresh |
search_term_report | Fields include customer_id, stat_dt, campaign_id, adgroup_id. | Incremental |
seasonal_event_master_report | Fields include id, event_name, super_event_id, level. | Full refresh |
shared_budget | Fields include customer_id, budget_lock, daily_budget, delivery_method. | Incremental |
shared_budget_master_report | Fields include customer_id, shared_budget_id, name, daily_budget. | Full refresh |
shopping_product_conversion_report | Fields include customer_id, stat_dt, campaign_id, adgroup_id. | Incremental |
shopping_product_master_report | Fields include customer_id, ncc_adgroup_id, ncc_ad_id, inspect_status. | Full refresh |
shopping_product_report | Fields include customer_id, stat_dt, campaign_id, adgroup_id. | Incremental |
shopping_search_term_conversion_report | Fields include customer_id, stat_dt, campaign_id, adgroup_id. | Incremental |
shopping_search_term_report | Fields include customer_id, stat_dt, campaign_id, adgroup_id. | Incremental |
target | Fields include customer_id, ncc_target_id, owner_id, target_tp. | Incremental |
time_contract | Fields include customer_id, adgroup_name, adgroup_template_name, cancel_customer_id. | Full refresh |
Schema
Data model at a glance
ad
customer_idintegeradjsonad_attrjsonedit_tmstringenablebooleaninspect_statusstringncc_ad_idstringncc_adgroup_idstring
ad_account
customer_idintegerad_account_nointegercreated_atstringfavoritebooleanlast_access_timestringnaver_idstringrole_namestringad_account__countrystring
ad_asset_link_master_report
customer_idintegerasset_link_idstringasset_idstringncc_ad_idstringlink_tpintegerpinstringreg_tmstringdel_tmstring
ad_conversion_detail_report
customer_idintegerstat_dtstringcampaign_idstringadgroup_idstringkeyword_idstringad_idstringbusiness_channel_idstringhrsstring
ad_conversion_report
customer_idintegerstat_dtstringcampaign_idstringadgroup_idstringkeyword_idstringad_idstringbusiness_channel_idstringmedia_codestring
ad_detail_report
customer_idintegerstat_dtstringcampaign_idstringadgroup_idstringkeyword_idstringad_idstringbusiness_channel_idstringhrsstring
No verified relationships are available in this schema preview.
Connector pairings
Popular destinations
Commonly paired with Naver Ads in Extract workflows.
Why Extract
Why Extract for Naver Ads
- Rust-native performanceUse Rust-native data movement to refresh Naver Ads reporting every 15 minutes, hourly, daily, or on a custom schedule as volume grows.
- Full run transparencyInspect Naver Ads API activity, execution steps, and timing in Extract's run-level logs when data needs review.
- ELT + Reverse ETL in oneCombine Naver Ads data with customer and finance models, then send approved outputs through a separately configured Reverse ETL destination.
FAQ
Frequently asked questions
How does Extract handle incremental and full Naver Ads syncs?
An incremental sync processes only new or changed data since a stored checkpoint or new date partition, while a full sync processes the complete selected dataset or date range again. By avoiding repeated processing and writes for the full dataset, incremental syncs can reduce destination database updates and warehouse compute costs. Stream schemas define full refresh, incremental changes, partition-based extraction. Behavior varies by stream and configuration. Extract records run details so teams can verify each sync.
Can I backfill historical Naver Ads data with Extract?
Historical coverage for Naver Ads: Backfill (Days) (backfill): The backfill setting revisits and updates data from the past X days, ensuring the most current and accurate information replaces any previously pulled data. Use the setup guide and run details to confirm the available source records and selected settings.
How can teams monitor Naver Ads data quality and freshness?
Compare expected reporting periods and record totals in your models, then use Extract's run-level logs to inspect Naver Ads API activity, execution steps, and timing. This helps teams distinguish a source-data delay from a failed or incomplete run.
How often can Extract sync data from Naver Ads?
Extract supports schedules every 15 minutes, hourly, daily, or on a custom cadence. Teams can choose a frequency that matches routine reporting, time-sensitive monitoring, or operational activation needs.
What does the Naver Ads data model look like in the destination?
The Available streams table describes the datasets Extract can read from Naver Ads. The inline schema previews entities and fields. Only relationships verified from the exported schema are shown. Use the full schema link for more details.