On This Page
Effective August 05, 2026, Hevo supports Google Ads API v24, which includes enhanced reporting capabilities. To ensure uninterrupted service, your Pipelines were automatically upgraded. As part of this upgrade, the new API version has deprecated and introduced the following fields for the corresponding reports:
| Report | Changes |
|---|---|
| Ad Group | Added Fields: ad_group.demand_gen_ad_group_settings.channel_controls.selected_channels.maps, ad_group.effective_target_cpc, ad_group.effective_target_cpc_source, ad_group.target_cpc_micros, ad_group.vertical_ads_format_setting.disable_text_ads, ad_group.vertical_ads_format_setting.enable_booking_links, ad_group.vertical_ads_format_setting.enable_vertical_promotion_ads |
| Ad Group Ad |
Removed Fields: ad_group_ad.ad.call_ad.business_name, ad_group_ad.ad.call_ad.call_tracked, ad_group_ad.ad.call_ad.conversion_action, ad_group_ad.ad.call_ad.conversion_reporting_state, ad_group_ad.ad.call_ad.country_code, ad_group_ad.ad.call_ad.description1, ad_group_ad.ad.call_ad.description2, ad_group_ad.ad.call_ad.disable_call_conversion, ad_group_ad.ad.call_ad.headline1, ad_group_ad.ad.call_ad.headline2, ad_group_ad.ad.call_ad.path1, ad_group_ad.ad.call_ad.path2, ad_group_ad.ad.call_ad.phone_number, ad_group_ad.ad.call_ad.phone_number_verification_url, ad_group_ad.ad.demand_gen_multi_asset_ad.lead_form_only Added Fields: ad_group_ad.ad.demand_gen_multi_asset_ad.classic_display_images, ad_group_ad.ad.demand_gen_multi_asset_ad.classic_display_images.asset, ad_group_ad.ad.demand_gen_video_responsive_ad.companion_banners, ad_group_ad.ad.demand_gen_video_responsive_ad.companion_banners.asset, ad_group_ad.ad.synthetic_content_info.advertiser_attestation.source, ad_group_ad.ad.synthetic_content_info.advertiser_attestation.status, ad_group_ad.ad.synthetic_content_info.system_attestation.source, ad_group_ad.ad.synthetic_content_info.system_attestation.status, ad_group_ad.ad.video_responsive_ad.business_name, ad_group_ad.ad.video_responsive_ad.logo_images, ad_group_ad.ad.video_responsive_ad.logo_images.asset, ad_group_ad.start_date_time, ad_group_ad.end_date_time |
| Asset Group | Added Fields: asset_group.google_local_services_info.callouts, asset_group.google_local_services_info.category_id |
| Asset Group Asset | Removed Fields: asset_group_asset.performance_label |
| Campaign |
Removed Fields: campaign.start_date, campaign.end_date, campaign.url_expansion_opt_out, campaign.video_brand_safety_suitability Added Fields: campaign.start_date_time, campaign.end_date_time, campaign.feed_types, campaign.hotel_setting.disable_hotel_setting, campaign.pmax_campaign_settings.local_services_enabled, campaign.pmax_campaign_settings.local_services_pmax_campaign_settings.country_code, campaign.pmax_campaign_settings.local_services_pmax_campaign_settings.founding_year, campaign.pmax_campaign_settings.local_services_pmax_campaign_settings.navigational_query_leads_enabled, campaign.pmax_campaign_settings.local_services_pmax_campaign_settings.phone_numbers, campaign.shopping_setting.ignore_brand_exclusion_in_shopping_ads, campaign.target_cpc.target_cpc_micros, campaign.text_guidelines.messaging_restrictions, campaign.text_guidelines.term_exclusions, campaign.video_campaign_settings.booking_details.cancellation_date_time, campaign.video_campaign_settings.booking_details.hold_expiration_date_time, campaign.video_campaign_settings.booking_details.status, campaign.video_campaign_settings.reservation_ad_category_self_disclosure.alcohol, campaign.video_campaign_settings.reservation_ad_category_self_disclosure.gambling, campaign.video_campaign_settings.reservation_ad_category_self_disclosure.politics, campaign.view_through_conversion_optimization_enabled |
| Cart Data Sales View | Added Fields: cart_data_sales_view.resource_name |
| Experiment | Added Fields: experiment.optimize_assets_experiment.optimize_assets_experiment_subtype, experiment.video_experiment.video_experiment_subtype |
| Matched Location Interest View | Added Fields: matched_location_interest_view.resource_name |
| Metrics (shared across applicable reports) |
Removed Fields: metrics.average_cpv, metrics.video_view_rate, metrics.video_view_rate_in_feed, metrics.video_view_rate_in_stream, metrics.video_view_rate_shorts, metrics.video_views, metrics.asset_best_performance_cost_percentage, metrics.asset_best_performance_impression_percentage, metrics.asset_good_performance_cost_percentage, metrics.asset_good_performance_impression_percentage, metrics.asset_learning_performance_cost_percentage, metrics.asset_learning_performance_impression_percentage, metrics.asset_low_performance_cost_percentage, metrics.asset_low_performance_impression_percentage, metrics.asset_unrated_performance_cost_percentage, metrics.asset_unrated_performance_impression_percentage, metrics.sample_best_performance_entities, metrics.sample_good_performance_entities, metrics.sample_learning_performance_entities, metrics.sample_low_performance_entities, metrics.sample_unrated_performance_entities Added Fields: metrics.active_view_audibility_invalid_givt_measurable_impressions_rate, metrics.active_view_audibility_invalid_measurable_impressions_rate, metrics.active_view_audibility_measurable_impressions, metrics.active_view_audibility_measurable_impressions_rate, metrics.active_view_audible_impressions, metrics.active_view_audible_impressions_rate, metrics.active_view_audible_quartile_p100_rate, metrics.active_view_audible_quartile_p25_rate, metrics.active_view_audible_quartile_p50_rate, metrics.active_view_audible_quartile_p75_rate, metrics.active_view_audible_thirty_seconds_impressions, metrics.active_view_audible_thirty_seconds_impressions_rate, metrics.active_view_audible_two_seconds_impressions, metrics.active_view_audible_two_seconds_impressions_rate, metrics.all_average_cart_size, metrics.all_average_order_value_micros, metrics.all_cost_of_goods_sold_micros, metrics.all_cross_sell_cost_of_goods_sold_micros, metrics.all_cross_sell_gross_profit_micros, metrics.all_cross_sell_revenue_micros, metrics.all_cross_sell_units_sold, metrics.all_gross_profit_margin, metrics.all_gross_profit_micros, metrics.all_lead_cost_of_goods_sold_micros, metrics.all_lead_gross_profit_micros, metrics.all_lead_revenue_micros, metrics.all_lead_units_sold, metrics.all_orders, metrics.all_revenue_micros, metrics.all_units_sold, metrics.average_video_watch_time_duration_millis, metrics.biddable_indirect_install_first_in_app_conversion_micros, metrics.clicks_margin_of_error, metrics.clicks_p_value, metrics.clicks_point_estimate, metrics.control_clicks, metrics.control_conversion_value, metrics.control_conversion_value_per_cost, metrics.control_conversions, metrics.control_cost_micros, metrics.control_cost_per_conversion, metrics.control_impressions, metrics.conversion_value_change_point_estimate, metrics.conversion_value_margin_of_error, metrics.conversion_value_p_value, metrics.conversion_value_per_cost_change_point_estimate, metrics.conversion_value_per_cost_margin_of_error, metrics.conversion_value_per_cost_p_value, metrics.conversions_absolute_change_margin_of_error, metrics.conversions_absolute_change_p_value, metrics.conversions_absolute_change_point_estimate, metrics.cost_micros_change_point_estimate, metrics.cost_micros_margin_of_error, metrics.cost_micros_p_value, metrics.cost_per_conversion_change_point_estimate, metrics.cost_per_conversion_margin_of_error, metrics.cost_per_conversion_p_value, metrics.cross_device_conversions_by_conversion_date, metrics.cross_device_conversions_value_by_conversion_date, metrics.impressions_margin_of_error, metrics.impressions_p_value, metrics.impressions_point_estimate, metrics.svr, metrics.trueview_average_cpv, metrics.unique_users_five_plus, metrics.unique_users_four_plus, metrics.unique_users_ten_plus, metrics.unique_users_three_plus, metrics.unique_users_two_plus, metrics.video_trueview_view_rate, metrics.video_trueview_view_rate_in_feed, metrics.video_trueview_view_rate_in_stream, metrics.video_trueview_view_rate_shorts, metrics.video_trueview_views, metrics.video_watch_time_duration_millis |
| Per Store View | Added Fields: per_store_view.address1, per_store_view.address2, per_store_view.business_name, per_store_view.city, per_store_view.country_code, per_store_view.phone_number, per_store_view.postal_code, per_store_view.province |
| Segments (shared across applicable reports) | Added Fields: segments.ad_sub_network_type, segments.ad_using_product_data, segments.ad_using_video, segments.mobile_device_platform, segments.product_sold_brand, segments.product_sold_category_level1, segments.product_sold_category_level2, segments.product_sold_category_level3, segments.product_sold_category_level4, segments.product_sold_category_level5, segments.product_sold_condition, segments.product_sold_custom_attribute0, segments.product_sold_custom_attribute1, segments.product_sold_custom_attribute2, segments.product_sold_custom_attribute3, segments.product_sold_custom_attribute4, segments.product_sold_item_id, segments.product_sold_title, segments.product_sold_type_l1, segments.product_sold_type_l2, segments.product_sold_type_l3, segments.product_sold_type_l4, segments.product_sold_type_l5, segments.vertical_ads_event_participant_display_names, segments.vertical_ads_hotel_class, segments.vertical_ads_listing, segments.vertical_ads_listing_brand, segments.vertical_ads_listing_city, segments.vertical_ads_listing_country, segments.vertical_ads_listing_region, segments.vertical_ads_listing_user_rating, segments.vertical_ads_listing_venue, segments.vertical_ads_partner_account, segments.vertical_ads_vertical |
| Shopping Product | Added Fields: shopping_product.product_image_uri |
| Targeting Expansion View | Added Fields: targeting_expansion_view.resource_name |
| Video Enhancement | Added Fields: video_enhancement.duration_millis, video_enhancement.resource_name, video_enhancement.source, video_enhancement.title |
Note: Hevo no longer supports ingesting data for the fields and metrics listed as Removed Fields. If your custom reports use these fields, Hevo may populate NULL values in the corresponding Destination columns. To avoid this, update your custom reports to use the supported fields as per Google Ads API v24.
This upgrade ensures that all the newly added resources, including attributes, metrics, and segments, are added to your reports. The upgrade process was seamless, with no downtime for your Pipelines. This change applies to all new and existing Pipelines created with this Source.
Google Ads is an advertising platform by Google that allows businesses to create ads for their products and services. It also provides statistics for these ads to gather insights and grow your business faster.
Hevo uses the Google Ads API to ingest data from your Google Ads account and replicate it into the Destination of your choice. The Google Ads API is the next generation of Google AdWords API. It provides you with new features and improvements over the AdWords API that make it easy for you to manage large and complex accounts.
Prerequisites
-
An active Google Ads account from which data is to be ingested. Contact the administrator of your Google Ads account if you do not have access.
-
Access to the manager account if the Google Ads account is linked to a manager account.
-
You are assigned the Team Administrator, Team Collaborator, or Pipeline Administrator role in Hevo to create the Pipeline.
Granting Access to your Google Ads Account (Optional)
Note: You can invite other users to access your Google Ads account data only if you are the administrator of the account.
-
Sign in to your Google Ads account.
-
In the left navigation bar, click the Admin (
) icon, and then click Access and security.
-
In the Access and security screen, click the Users tab, and then click the Plus (
) icon.
-
In the Invite others to access… screen:
-
Specify the user’s email address associated with a Google account. The user must create a Google account if they do not have one.
-
Select a value from the Access Expires drop-down list to set an expiration date for the invited user’s access to your Google Ads account.
-
Select the account access level. You should provide at least Read-only access.
-
-
Click Send invitation.
The invited users are displayed in the Pending invitations section. You can click Revoke in the Actions column if you need to withdraw the invitation.
After the user accepts the email invitation, you receive a notification in your account.
Configuring Google Ads as a Source
Perform the following steps to configure Google Ads as the Source in your Pipeline:
-
Click PIPELINES in the Navigation Bar.
-
Click + Create Pipeline in the Pipelines List View.
-
On the Select Source Type page, select Google Ads.
-
On the Select Destination Type page, select the type of Destination you want to use.
-
On the Configure your Google Ads page, do one of the following:
-
Select a previously configured account and click Continue.
-
Click + Add Google Ads Account and perform the following steps to configure an account:
-
Log in to your Google Ads account.
-
Click Allow to authorize Hevo to access your Google Ads data.
-
-
-
On the Configure your Google Ads Source page, specify the following:
-
Pipeline Name: A unique name for your Pipeline, not exceeding 255 characters.
-
Authorized User Account (Non-editable): The email address that you selected when connecting to your Google Ads account. This value is pre-filled.
-
Google Ads API Version: The API version that you want to use to ingest data from the Source.
-
Ad Accounts: The Google Ads account(s) from where you want to replicate the data.
-
Select Report Type: Select one of the following report types to ingest data from your Google Ads reports:
-
Standard Reports: Hevo provides you a few reports that Google creates based on a valid combination of metrics and dimensions. These reports can be used according to your requirements, in order to replicate data from the report to your desired Destination quickly and efficiently. Refer to section, Standard Reports for steps to configure this.
-
Custom Reports: Hevo allows you to create your own reports by selecting the metrics and dimensions you need. Then, the data from these reports is replicated to your desired Destination. Refer to section, Custom Reports for steps to configure this.
-
-
-
Click Continue.
-
Proceed to configuring the data ingestion and setting up the Destination.
Standard Reports
Hevo provides you with a few standard reports for ease of configuration that you can use according to your requirements. It automatically identifies the metrics and dimensions based on the Google Ads report that you select for replicating data to your desired Destination.
To configure standard reports, specify the following:
-
Report Names: The report(s) whose data you want to replicate to your Destination.
-
Aggregation Window: The duration for which the data in the report(s) is aggregated. Aggregation is done on a daily basis. Default duration: Daily.
-
Daily: Aggregates the data present in the reports once a day daily.
-
Weekly: Aggregates the data present in the reports for the last week.
-
Monthly: Aggregates the data present in the reports for the last month.
-
-
Conversion Window (in days): The duration at which you want the data to be refreshed to capture conversions.
Default duration: 90 days
Min duration: 30 days
Max duration: 90 days
Note: The conversion window in your Google Ads account remains unaffected by the conversion window that you specify in Hevo either during or post-Pipeline creation. For example, let us say you set a conversion window of 60 days in your Google Ads account, and a conversion window of 30 days in Hevo. Then, the conversion window in your Google ads account remains unaffected by the conversion window that you specified in Hevo.
-
Historical Sync Duration: The duration for which you want to ingest existing data from the Source. This cannot be changed after the Pipeline is created. Default duration: 1 Year.
Note: If you select All Available Data, Hevo ingests all the data available in your Google Ads account since January 01, 2011.
Note: You can only modify the Aggregation Window and Conversion Window post-Pipeline creation.
Custom Reports
Hevo allows you to create your own reports by choosing a valid combination of metrics and dimensions. You can manually select these metrics and dimensions in Hevo to replicate the data from these reports to your desired Destination. Read Creating a Custom Report to learn more about creating your own reports and validating the compatibility of the selected combination of segments, dimensions, and metrics.
To configure custom reports, specify the following:
-
Report Name: The report(s) whose data you want to replicate to your Destination.
-
Segments: The criteria for organizing the data retrieved from an ad campaign. These are displayed based on the report you selected above.
Note: You must always select Date from the drop-down list of Segments along with the ones that you want to use.
-
Dimensions: The categories and sub-categories to filter the data retrieved from an ad campaign, as per your requirements. These dimensions are displayed based on the Segments you selected above.
-
Metrics: The various parameters that enable you to quantitatively measure the data retrieved from an ad campaign. These metrics are displayed based on the Dimensions you selected above.
Note: Only the Metrics and Dimensions compatible with the Segments selected above are available for selection. Refer to section, Source Considerations.
-
Aggregation Window: The duration for which the data in the report(s) is aggregated. Aggregation is done on a daily basis. Default duration: Daily.
-
Daily: Aggregates the data present in the reports once a day daily.
-
Weekly: Aggregates the data present in the reports for the last week.
-
Monthly: Aggregates the data present in the reports for the last month.
-
-
Attributed & Segmenting Resources: The dimensions of the resources that you want to replicate. These are displayed based on the report you selected above.
-
Conversion Window (in days): The duration at which you want the data to be refreshed to capture conversions.
Default duration: 90 days.
Min duration: 30 days
Max duration: 90 days.
Note: The conversion window in your Google Ads account remains unaffected by the conversion window that you specify in Hevo either during or post-Pipeline creation. For example, let us say you set a conversion window of 60 days in your Google Ads account, and a conversion window of 30 days in Hevo. Then, the conversion window in your Google ads account remains unaffected by the conversion window that you specified in Hevo.
-
Historical Sync Duration: The duration for which you want to ingest existing data from the Source. This cannot be changed after the Pipeline is created. Default duration: 1 Year.
Note: If you select All Available Data, Hevo ingests all the data available in your Google Ads account since January 01, 2011.
Note: You can only modify the Aggregation Window and Conversion Window post-Pipeline creation.
Data Replication
| For Teams Created | Default Ingestion Frequency | Minimum Ingestion Frequency | Maximum Ingestion Frequency | Custom Frequency Range (in Hrs) |
|---|---|---|---|---|
| Before Release 2.21 | 12 Hrs | 15 Mins | 24 Hrs | 1-24 |
| After Release 2.21 | 12 Hrs | 30 Mins | 24 Hrs | 1-24 |
-
Historical Data:
-
For Pipelines created before Release 1.63: In the first run of the Pipeline, Hevo fetches the data of all the objects and reports available in your account for the past one year and loads it to the Destination. In case of the Click View report, Hevo fetches the data for the past 90 days and loads it to the Destination.
-
For Pipelines created after Release 1.63: In the first run of the Pipeline, Hevo fetches the data of all the objects and reports available in your account for the past one year and loads it to the Destination. This default duration of one year can be changed as per the user’s requirement.
From Release 1.79 onwards, Hevo ingests the historical data for all the objects using the Recent Data First approach. This enables you to have quicker access to the most recent data. This change applies to all new and existing Pipelines.
-
-
Incremental Data: Once the historical data ingestion is complete, every subsequent run of the Pipeline fetches new and updated data for the objects and reports as per the ingestion frequency.
-
Data Refresh: Hevo refreshes the data based on the specified conversion window. For example, if the conversion window is 30, Hevo refreshes the data for the last 30 days from today.
Schema and Primary Keys
Hevo uses the following schema to upload the records in the Destination database:
| Report | Primary Key |
|---|---|
| Ad Group | ad_group.resource_name |
| Ad Group Ad | ad_group_ad.resource_name |
| Ad Group Ad Asset Combination View | ad_group_ad_asset_combination_view.resource_name |
| Ad Group Ad Asset View | ad_group_ad_asset_view.resource_name |
| Ad Group Asset | ad_group_asset.resource_name |
| Ad Group Audience View | ad_group_audience_view.resource_name |
| Ad Schedule View | ad_schedule_view.resource_name |
| Age Range View | age_range_view.resource_name |
| Asset Field Type View | asset_field_type_view.resource_name |
| Asset Group Product Group View | asset_group_product_group_view.resource_name |
| Asset Set Asset | asset_set_asset.resource_name |
| Asset Set Type View | asset_set_type_view.resource_name |
| Bidding Strategy | bidding_strategy.resource_name |
| Campaign | campaign.resource_name |
| Campaign Asset | campaign_asset.resource_name |
| Campaign Audience View | campaign_audience_view.resource_name |
| Campaign Budget | campaign_budget.resource_name |
| Campaign Group | campaign_group.resource_name |
| Click View | click_view.resource_name |
| Customer | customer.resource_name |
| Customer Asset | customer_asset.resource_name |
| Customer Search Term Insight | customer_search_term_insight.resource_name |
| Detail Placement View | detail_placement_view.resource_name |
| Display Keyword View | display_keyword_view.resource_name |
| Distance View | distance_view.resource_name |
| Dynamic Search Ads Search Term View | dynamic_search_ads_search_term_view.resource_name |
| Expanded Landing Page View | expanded_landing_page_view.resource_name |
| Gender View | gender_view.resource_name |
| Geographic View | geographic_view.resource_name |
| Group Placement View | group_placement_view.resource_name |
| Hotel Group View | hotel_group_view.resource_name |
| Hotel Performance View | hotel_performance_view.resource_name |
| Hotel Reconciliation | hotel_reconciliation.resource_name |
| Income Range View | income_range_view.resource_name |
| Keyword View | keyword_view.resource_name |
| Label | label.resource_name |
| Landing Page View | landing_page_view.resource_name |
| Location View | location_view.resource_name |
| Managed Placement View | managed_placement_view.resource_name |
| Paid Organic Search Term View | paid_organic_search_term_view.resource_name |
| Parental Status View | parental_status_view.resource_name |
| Product Group View | product_group_view.resource_name |
| Search Term View | search_term_view.resource_name |
| Shopping Performance View | shopping_performance_view.resource_name |
| Smart Campaign Search Term View | smart_campaign_search_term_view.resource_name |
| Topic View | topic_view.resource_name |
| Travel Activity Group View | travel_activity_group_view.resource_name |
| Travel Activity Performance View | travel_activity_performance_view.resource_name |
| User Location View | user_location_view.resource_name |
| Video | video.resource_name |
| Webpage View | webpage_view.resource_name |
Reports: Hevo attaches the following fields to all the report Events ingested from Google Ads API:
-
__hevo_report_<aggregation window>: The date, week, or month for which the report is generated. The name of the field depends on the aggregation window you select while configuring the Pipeline. For example:-
If you select the aggregation window as Daily, the field name is
__hevo_report_date. -
If you select aggregation window as Weekly, the field name is
__hevo_report_week. -
If you select aggregation window as Monthly, the field name is
__hevo_report_month.
-
-
__hevo_id: The unique ID of the Google Ads Event. Hevo derives this by hashing multiple fields from the standard and custom reports. Read Metadata Column __hevo_id.
Data Model
The following is the list of tables (reports) that are created at the Destination when you run the Pipeline:
| Report | Description |
|---|---|
| Ad Group | Contains details of an ad group created in your Google Ads account. For example, its name, status, type, target customers, and the campaign to which the ad group belongs. An ad group contains one or more ads that have a common target audience. |
| Ad Group Ad | Contains details of an ad in an ad group. For example, its ID, status, and the ad group that the ad belongs to. |
| Ad Group Ad Asset View | Contains details of the performance and reach of the assets associated with an ad group ad. For example, its ID, role in the ad, and the ad to which it is associated. |
| Ad Group Ad Asset Combination View | Contains details of the various combinations of ad assets used in an ad group. This enables you to optimize the performance of your ad campaigns. |
| Ad Group Asset | Contains details of the assets associated with an ad group. For example, its ID, status, and role in the ad group. |
| Ad Group Audience View | Contains details of the performance and reach of an ad group through various resources, such as searches and or YouTube ads. This performance data is aggregated at the target audience level. |
| Ad Schedule View | Contains details of the performance and reach of an ad campaign, aggregated according to its schedule. |
| Age Range View | Contains details of the performance and reach of an ad campaign, aggregated according to the age range of its target audience. |
| Asset Field Type View | Contains details of the performance and reach of each asset that is being used as an extension. |
| Asset Group Product Group View | Contains details of the performance of product groups within an asset group. |
| Asset Set Asset | Contains details of the association between an asset and an asset set. |
| Asset Set Type View | Contains details of the performance of asset sets in campaigns. This enables you to optimize these campaigns. |
| Bidding Strategy | Contains details of the bidding strategy that you use for your campaigns. For example, it’s ID, name, status, currency, and the campaigns it is used in. A bidding strategy is when you set an average bid that you are willing to spend to maximize impressions on your campaigns. |
| Campaign | Contains details of the ad campaigns running in your account. For example, its ID, name, status, budget, and bidding strategy. An ad campaign consists of one or more ad groups that are used to advertise the products or services provided by your organization. |
| Campaign Asset | Contains details of the assets used in an ad campaign. For example, its status and role in the campaign. |
| Campaign Audience View | Contains details of the performance and reach of an ad group through various resources, such as searches and or YouTube ads. This performance data is aggregated at the target audience and campaign level. |
| Campaign Budget | Contains details of the budget that you have set for one or more campaigns. For example, it’s ID, name, amount, currency, and the number of campaigns using this budget. |
| Campaign Group | Contains details of the organization and management of your ad campaigns. This enables you to optimize strategies and better analyze performance statistics. |
| Click View | Contains details of the performance and reach of a campaign, in terms of the clicks and interactions. |
| Customer | Contains details of the users to whom you are advertising your product or service. |
| Customer Asset | Contains details of the assets available in your Google Ads account. |
| Customer Search Term Insight | Contains details of the search terms that triggered the display of your ads to an audience. |
| Detail Placement View | Contains details of the performance and reach of an ad group on the basis of location where you are advertising it, such as YouTube, website, and mobile application. |
| Display Keyword View | Contains details of the performance and reach of keywords that you use in an ad group for it to be visible to the audience on the basis of their browsing history or other details. |
| Distance View | Contains details of the performance and reach on ad groups on the basis of distance between your advertising location and the location of a customer. |
| Dynamic Search Ads Search Term View | Contains details of the performance and reach of the frequently searched terms and phrases, and how your ads are displayed when someone searches for these terms. |
| Expanded Landing Page View | Contains details of the performance and reach of an ad group on the basis of the expanded final URL. An expanded final URL is the link to the relevant page where your ad is shown to the users on the basis of their searched keywords. |
| Gender View | Contains details of the performance and reach of an ad group on the basis of gender of the viewers. |
| Geographic View | Contains details of the performance and reach of an ad group on the basis of country. |
| Group Placement View | Contains details of the performance and reach of your ad group on the channels where they appear on YouTube or Google display network. For example, a website, a YouTube channel, or a mobile application. |
| Hotel Group View | Contains details of the performance and reach of one or more ads created in your Google Ads account to advertise your hotels. |
| Hotel Performance View | Contains details of the performance and reach of hotel groups on the basis of the clicks and impressions. |
| Hotel Reconciliation | Contains details of the reconciliation of hotel bookings to your advertisements. |
| Income Range View | Contains details of the performance and reach of an ad group on the basis of the income range of your target audience. |
| Keyword View | Contains details of the performance and reach of the words or phrases that help in displaying your ads when people search for these words. |
| Label | Contains details of the labels defined in your Google Ads account, such as name, status, background color, and description. Labels allow you to group and organize entities, such as campaigns, ad groups, ads, or keywords, for easier filtering and reporting. Note: If only label is selected in a standard report, the Aggregation Window and Conversion Window fields are grayed out and become unavailable for selection. |
| Landing Page View | Contains details of the performance and reach of an ad group aggregated on the basis of the landing page unexpanded URL. An unexpanded URL does not contain any contextual keywords or other parameters that may be added to an expanded URL. |
| Location View | Contains details of the performance and reach of an ad campaign on the basis of target location. |
| Managed Placement View | Contains details of the performance and reach of the placement criteria set for targeting of ads. A placement criteria contains the internet locations where you want to display your ads. |
| Paid Organic Search Term View | Contains details of the performance of your ads against the paid and organic search terms. This enables you to optimize your ads for visibility and engagement. |
| Parental Status View | Contains details of the performance and reach of the ads rolled out targeted at users who are parents. |
| Product Group View | Contains details of the performance and reach of the groups in which your products are categorized. |
| Search Term View | Contains details of the performance and reach of an ad group on the basis of the terms searched by the users in the search network. |
| Shopping Performance View | Contains details of the performance and reach of a shopping campaign on the basis of the product characteristics, such as brand, category, and product type. |
| Smart Campaign Search Term View | Contains details of the performance and reach of the smart campaigns in your Google Ads account. A smart campaign helps draw customers to buy the products or services you are offering by highlighting the various attractive features of your business. |
| Topic View | Contains details of the performance and reach of the ads appearing on YouTube or the Google display network pages that contain the information related to your specific topics. For example, let us say your topic is goods transfer, then your ads may be listed on pages that contain information related to commercial vehicles, packing and moving, and so on. |
| Travel Activity Group View | Contains details of the performance of the travel-related campaigns containing various travel activities. This enables you to optimize your campaigns as per the travel interests of the audience. |
| Travel Activity Performance View | Contains details of the performance of each travel-related ad within your campaign. This enables you to optimize strategies and returns. |
| User Location View | Contains details of the performance and reach of your ads on the basis of the physical location of your target audience. |
| Video | Contains details of the videos that you can create to advertise your products to the target audience on YouTube or the Google display network. |
| Webpage View | Contains details of the performance and reach of your ads on the pages where they are displayed. |
Additional Information
Read the detailed Hevo documentation for the following related topics:
Source Considerations
-
Google Ads does not support custom metrics and dimensions in the reports.
-
For custom reports, you can only select the metrics and dimensions that are compatible with the segments you select. Read Segments to know more about the segments in Google Ads, and the metrics and dimensions compatible with these segments.
-
The Google Ads API does not return any Events in the report if an ad did not get any impressions. Therefore, the schema for that ad is not created in your Destination. This is because the Google Ads API does not support the includeZeroImpressions parameter.
-
The Google Ads API uses a querying approach to fetch data from your Google Ads account. Therefore, there are no readily available reports in Google Ads. Hevo aggregates the data in your Google Ads account and generates a report using the segments, dimensions, and metrics of the various resources in your account. It results in a higher number of ingestions for your Hevo Google Ads Pipeline. For example, let us say, while setting up your Pipeline in Hevo, you also set the aggregation window as last 30 days for 100 reports, and the ingestion frequency as 1 hour. Then, the number of reports ingested every 1 hour would be 30 x 100 = 3000 reports. In one day, the number of reports ingested would be 3000 x 24 = 72000 reports. As a result, the number of Events ingested per day is high.
-
Google Ads has removed support for exporting data for some Gmail-related metrics in the Ad Group Ad report in Version 12 of their API. As a result, from Release 2.09, Hevo does not support the ingestion of historical data for these metrics, and all existing Pipelines containing these metrics now load null values for these fields.
Limitations
-
Hevo does not fetch data for the metrics that are not filterable by the segment,
date. -
Hevo does not load data from a column into the Destination table if its size exceeds 16 MB, and skips the Event if it exceeds 40 MB. If the Event contains a column larger than 16 MB, Hevo attempts to load the Event after dropping that column’s data. However, if the Event size still exceeds 40 MB, then the Event is also dropped. As a result, you may see discrepancies between your Source and Destination data. To avoid such a scenario, ensure that each Event contains less than 40 MB of data.
-
By default, Hevo schedules data ingestion based on Coordinated Universal Time (UTC), regardless of your Source account’s time zone. This can cause delays if the account operates in a different time zone. To address this, Hevo allows you to align the data ingestion with your preferred time zone; contact Hevo Support.
Revision History
Refer to the following table for the list of key updates made to this page:
https://docs.hevodata.com
| Date | Release | Description of Change |
|---|---|---|
| Aug-05-2026 | 2.51.1 | Updated the warning container to include information about the upgrade to Google Ads API v24. |
| Apr-28-2026 | NA | Updated section, Configuring Google Ads as a Source to mention that the historical sync duration cannot be changed after the Pipeline is created. |
| Nov-06-2025 | NA | Updated the document as per the latest Hevo UI. |
| Sep-22-2025 | NA | Updated section, Prerequisites to add information about providing access to manager accounts. |
| Sep-18-2025 | NA | Updated section, Configuring Google Ads as a Source as per the latest UI. |
| Aug-15-2025 | 2.39.1 | - Updated the warning container in the page overview to mention about the version upgrade. - Updated sections, Schema and Primary Keys and Data Model to remove reports deprecated in the new API version. |
| Aug-12-2025 | 2.39 | Updated sections, Data Model and Schema and Primary Keys to add information about the Labels object. |
| Jul-07-2025 | NA | Updated the Limitations section to inform about the max record and column size in an Event. |
| Mar-21-2025 | 2.34.1 | Updated the Limitations section to add information on ingestion delay due to time zone. |
| Jan-31-2025 | 2.32.2 | - Removed section, Migrating Pipelines to Google Ads API V16. - Updated the warning container in the page overview to include information about the upgrade to Google Ads API v18 |
| Jan-07-2025 | NA | Updated the Limitations section to add information on Event size. |
| Jan-06-2024 | NA | Updated section, Granting Access to your Google Ads Account (Optional) as per the latest Google Ads UI. |
| Sep-30-2024 | 2.28.1 | Updated section, Data Replication to change the default ingestion frequency to 12 Hrs. |
| Aug-19-2024 | 2.26.3 | - Removed section, Migrating Pipelines to Google Ads API V15. - Added section, Migrating Pipelines to Google Ads API V16. |
| Mar-05-2024 | 2.21 | Updated the ingestion frequency table in the Data Replication section. |
| Nov-28-2023 | 2.18 | - Added section, Migrating Pipelines to Google Ads API V15. - Updated the page to add information about Google Ads API V15. |
| Jul-21-2023 | NA | Updated the page to add information according to the latest Hevo functionality. |
| Apr-04-2023 | NA | Updated section, Configuring Google Ads as a Source to update the information about historical sync duration. |
| Mar-09-2023 | 2.09 | - Updated section, Source Considerations to add information about Google Ads not exporting data for some metrics. - Updated section, Data Model to update the links of the reports to Version 12 of the Google Ads API. |
| Jan-10-2023 | NA | Updated section, Data Model to add descriptions for reports. |
| Oct-25-2022 | 2.00 | Added the section, Granting Access to your Google Ads Account with steps to provide other users access to the Google Ads account. |
| Sep-21-2022 | NA | New document. |