Stay organized with collectionsSave and categorize content based on your preferences.
You can use the web UI in Ads Data Hub to do many of the same tasks as you
would using the API. This guide shows how to create a report and then run it. To
get the most out of this tutorial, be sure you have linked at least one
advertising account before beginning. To learn how to link your advertising
accounts, seeLink accounts to Ads Data Hub.
Write your own SQL
In Ads Data Hub, open theReportspage.
Click+ Create report.
ClickSQLto open a blank report.
Copy the following SQL, and then paste it into the report editor. You can
substitutecm_dt_impressionswith a table from your linked ads data. For
example, if you have linked a Google Ads account, replacecm_dt_impressionswithgoogle_ads_impressions.
Note that your report has not been saved at this point. You'll save it after
testing in the next stage.
Test your SQL using the sandbox
You should test your SQL using the sandbox role before running it on
production data. This can help you find problems faster.
ClickRunwhile in the SQL editor view. TheNew jobpane opens.Note:TheNew jobpane is available when the SQL editor is open, and
is useful for testing and iterating on your report before committing
changes. Jobs run from this pane don't contribute to the execution
history of your saved report.
SelectADH Sandbox Customerfrom theAds data fromdrop-down.
Choose the BigQuery project, dataset, and table where your report results
should be saved.
The date range will be automatically updated to "Aug 17 - Sep 18, 2018" to
match the contents of our sandbox data.
ClickRun. Job status and details will be displayed below the SQL
editor.
After the job finishes running, open the results inBigQuery. You should see a table that
looks something like this:
Row
impressions
1
388204742
ClickDoneto leave the SQL editor once you're satisfied with the
results of your test report. You're ready to run it on real data.
Run your SQL query using your linked data
After testing your SQL using the sandbox role, you're ready to run it on real
data.
Enter a name for the report.
Configure the input and output for jobs run on this report:
Select a data source in theAds data fromfield. This should be the
Ads Data Hub account ID associated with the ads data you want to query.
Select a date range and time zone for the report. The report time zone
should match the time zone of the linked ads account, such as a Google
Ads account.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-11-11 UTC."],[[["\u003cp\u003eThis guide demonstrates how to create, test, and run a report in Ads Data Hub to measure Campaign Manager 360 Data Transfer impressions.\u003c/p\u003e\n"],["\u003cp\u003eUsers can modify the provided SQL query to analyze impressions from other datasets like Google Ads by substituting table names.\u003c/p\u003e\n"],["\u003cp\u003eBefore running on production data, it is recommended to test reports using the sandbox role and specified date ranges for faster problem identification.\u003c/p\u003e\n"],["\u003cp\u003eOnce tested, reports can be executed on real data by selecting the desired account ID, privacy mode, destination table, date range, and time zone within Ads Data Hub.\u003c/p\u003e\n"],["\u003cp\u003eThe term "Queries" is transitioning to "Reports" and might be used interchangeably in the interface and documentation.\u003c/p\u003e\n"]]],["To create and run a report in Ads Data Hub, first write SQL using the report editor, optionally replacing sample tables with your linked ads data tables. Test the SQL by running it within the sandbox, selecting the sandbox customer and a target project for results. Once satisfied, save the report, configure input (data source, date range, privacy settings) and output (target project) settings, then run it against real, linked data. Saved reports contain the query, input/output details, schedule, and execution information.\n"],null,["# Get started with the Ads Data Hub web UI\n\n| **Key Term:** A **query** is the SQL text that is the foundation of a report. A **report** is made up of multiple components including the query, input and output settings, schedule, and execution details.\n\nYou can use the web UI in Ads Data Hub to do many of the same tasks as you\nwould using the API. This guide shows how to create a report and then run it. To\nget the most out of this tutorial, be sure you have linked at least one\nadvertising account before beginning. To learn how to link your advertising\naccounts, see [Link accounts to Ads Data Hub](/ads-data-hub/marketers/guides/link-accounts).\n\n\nCreate your report with a template Write your own SQL\n\nWrite your own SQL\n------------------\n\n1. In Ads Data Hub, open the **Reports** page.\n2. Click **+ Create report**.\n3. Click **SQL** to open a blank report.\n4. Copy the following SQL, and then paste it into the report editor. You can\n substitute `cm_dt_impressions` with a table from your linked ads data. For\n example, if you have linked a Google Ads account, replace\n `cm_dt_impressions` with `google_ads_impressions`.\n\n SELECT COUNT(*) AS impressions FROM adh.cm_dt_impressions;\n\nNote that your report has not been saved at this point. You'll save it after\ntesting in the next stage.\n\nTest your SQL using the sandbox\n-------------------------------\n\nYou should test your SQL using the sandbox role before running it on\nproduction data. This can help you find problems faster.\n\n1. Click **Run** while in the SQL editor view. The **New job** pane opens. **Note:** The **New job** pane is available when the SQL editor is open, and is useful for testing and iterating on your report before committing changes. Jobs run from this pane don't contribute to the execution history of your saved report.\n2. Select **ADH Sandbox Customer** from the **Ads data from** drop-down.\n3. Choose the BigQuery project, dataset, and table where your report results should be saved.\n4. The date range will be automatically updated to \"Aug 17 - Sep 18, 2018\" to match the contents of our sandbox data.\n5. Click **Run**. Job status and details will be displayed below the SQL editor.\n6. After the job finishes running, open the results in\n [BigQuery](https://bigquery.cloud.google.com/). You should see a table that\n looks something like this:\n\n | Row | impressions |\n |-----|-------------|\n | 1 | 388204742 |\n\n7. Click **Done** to leave the SQL editor once you're satisfied with the\n results of your test report. You're ready to run it on real data.\n\nRun your SQL query using your linked data\n-----------------------------------------\n\nAfter testing your SQL using the sandbox role, you're ready to run it on real\ndata.\n\n1. Enter a name for the report.\n2. Configure the input and output for jobs run on this report:\n 1. Select a data source in the **Ads data from** field. This should be the Ads Data Hub account ID associated with the ads data you want to query.\n 2. Select a date range and time zone for the report. The report time zone should match the time zone of the linked ads account, such as a Google Ads account.\n 3. Under Privacy noise settings, we recommend to set the toggle to the Use noise position. [Learn more about privacy\n modes.](/ads-data-hub/marketers/guides/privacy-checks#privacy_modes)\n 4. Leave the [filtered row summary](/ads-data-hub/marketers/guides/run-queries#filtered_row_summary) in automatic mode.\n 5. Choose the BigQuery project, dataset, and table where your report results should be saved.\n3. Click **Save**.\n4. Click **Run**.\n\nTo learn more about advanced features of creating reports, such as parameters\nand schedules, see the detailed documentation in [Create and run\nreports](/ads-data-hub/marketers/guides/run-queries)."]]