Google Search Ads 360 - Migration Guide

Overview

The new Google Search Ads 360 data source has been designed using Kimball data modeling principles.

Below you can find the ERD diagram which allows you to get a high-level view of the data source capabilities: Google Search Ads 360 ERD.pdf

Consequently, statistics and entities will be extracted as separate report types.

• Entity Reports: These reports describe specific objects within an account hierarchy, such as ads and campaigns. They contain detailed descriptive data and unique identifiers that link them to other entities, serving as a catalog of objects within the account hierarchy.
• Statistics Reports: These reports include all metrics-related data for a specific date range. They provide primary keys that link them to entities and offer a comprehensive overview of performance metrics for in-depth analysis.

Please note that the Statistics Report types support Custom configuration flow, allowing you to tailor reports according to your specific requirements.

Additionally, enriched views with prefix mrt_ will be created in our CH storage with a full list of properties related to the dimension (customer_id, campaign_id, adgroup_id, etc.) you’ve selected for the statistics report.

For a better understanding of how to re-create the previously available prebuilt reports through the old Google Search Ads 360 (sunset on June 30th, 2024) in the new Google Search Ads 360 you can refer to the Mapping Fields correspondence table.

Prerequisites

1. 1Find the necessary report type in Fields mapping between old SA360 vs new SA360 if you want to replicate the old report types, otherwise if you want to build from scratch start from point 2
2. 2Have a valid connection for the new Google Search Ads 360
3. 3Select the necessary account on the 1-st step of the Extraction Flow - “Select accounts”

How to work with the new Google Search Ads 360

Let’s imagine that I want to replicate the ads_activities_by_device report type from the old Google Search Ads 360 (sunset on June 30th, 2024) to get performance data for ad-level data granularity segmented by conversions and devices which includes the following fields (dimension/properties/metrics):

• Date (sql_name: date) which is available in the report ad_group_ad
• Name (sql_name: name) which is available in the report ad_group_ad_entity
• Ad ID (sql_name: ad_id) which is available in the report ad_group_ad
• Name (sql_name: name) which is available in the report campaign_entity
• Campaign ID (sql_name: campaign_id) which is available in the report ad_group_ad
• Name (sql_name: name) which is available in the report ad_group_entity
• Ad Group ID (sql_name: ad_group_id) which is available in the report ad_group_ad
• Labels (sql_name: labels) which is available in the report ad_group_ad_entity
• Descriptive Name (sql_name: descriptive_name) which is available in the report customer_entity
• Account Type (sql_name: account_type) which is available in the report customer_entity
• Conversion Action Name (sql_name: conversion_action_name) which is available in the report ad_group_ad
• Device (sql_name: device) which is available in the report ad_group_ad
• All Conversions (sql_name: all_conversions) which is available in the report ad_group_ad
• All Conversions Value (sql_name: all_conversions_value) which is available in the report ad_group_ad
• All Conversions (sql_name: all_conversions) which is available in the report ad_group_ad
• Cross Device Conversions (sql_name: cross_device_conversions) which is available in the report ad_group_ad
• Cross Device Conversions Value (sql_name: cross_device_conversions_value) which is available in the report ad_group_ad
• Currency Code (sql_name: currency_code) which is available in the report customer_entity

To get the proper final mrt_ view with the required list of fields, follow our guide below or watch a short video guide.

Step 1. Setup extraction for Stats & Entity reports

Select the necessary Extraction Templates on the 2nd step to extract the stats and entity reports.

For our example, we need to configure the following reports:

1. 1Custom configurable report for ad_group_ad
2. 2Entity reports for customer_entity, campaign_entity, ad_group_entity, ad_group_ad_entity

Step 2. Wait for the data extraction to finish

Wait until the extraction orders are ready and the data is available in the CH database. At that point, the generation of the final iew(s) will be launched automatically.

Step 3. Find generated mrt views in Data Explorer

Wait until the m view(s) is/are generated and shown on UI as a new table in “Data Explorer” (per each stats report will be generated one enriched view): Mrt Google Search Ads 360 {Stats Report Name}, Mrt Google Search Ads 360 Ads Conversion Device for our example. Please note that it can take up to 30 minutes for Mrt data table to be generated.

The final mrt naming convention is mrt_{{data_source_title}}_{{datatable_name}}:

• data_source_title - the title of the data source in the snake case e.g. Google Search Ads 360 → google_search_ads_360
• datatable_name - the data table name set on the 3-rd step of the extraction flow “Configure extraction” for the main statistics report in the snake case e.g. Ads Conversion Device - ads_conversion_device

For our example, the final view name for the data table Mrt Google Search Ads 360 Ads Conversion Device will be: mrt_google_search_ads_360_ads_conversion_device.

Please note:

• The final mrt view will include all properties without the possibility of specifying the list
• Custom columns are not currently supported, but they are in the implementation phase and should be available very soon
• Selected properties in the final mrt view follow this naming convention: {entity_name}_{field_name} (e.g., account_type from Customer Entity will resolve to customer_account_type)

Q&A