Stay organized with collections
Save and categorize content based on your preferences.
As a tool to help you operate more effectively amidst privacy checks in Ads Data Hub, the platform includes a synthetic dataset. Unlike normal data, this dataset isn’t subject to privacy checks, and as such should be used for experimentation and query development. The sandbox can improve your query development workflow by:
Running jobs faster. Because queries run on sandbox data aren't subject to privacy checks, your jobs will run faster.
Allowing you to inspect the underlying data. You can use SELECT * on sandbox data, giving you a better understanding of how your results could look.
Avoiding difference checks. Difference checks look at your query history, but aren't impacted by queries run on sandbox data. Learn more about difference checks
These improvements allow you to iterate on draft queries faster and can reduce the frequency of errors due to privacy checks. As such, Ads Data Hub recommends that you use sandbox data to develop queries whenever possible.
Sandbox data and privacy restrictions
Because the sandbox data is synthetic, Ads Data Hub relaxes certain privacy restrictions. For example, the following actions are only possible when querying sandbox data:
Running queries using SELECT *.
Running a series of similar queries. This is a common practice for
developing SQL queries, but doing so without using sandbox data makes it
more likely that your jobs will run into privacy check issues. Jobs run on
sandbox data won't impose data difference checks, allowing you to more
rapidly iterate on SQL. Learn more about privacy checks in
Ads Data Hub
Sandbox query workflow
The workflow for developing queries that use sandbox data is nearly identical to developing queries that use your own data. The only differences are:
When querying sandbox data, you can write queries that use SELECT *.
The date range will be automatically updated to "Aug 17 - Sep 18, 2018" to
match the contents of our sandbox data.
Sandbox jobs won't contribute to the execution history of your report.
To run queries on sandbox data, you must:
Run jobs from within the SQL editor of your report.
Select ADH Sandbox Customer from the Ads data from drop-down.
If you're using the API, you must use the specific sandbox account ID for
your region:
[[["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\u003eAds Data Hub provides a synthetic dataset sandbox to help users experiment and develop queries without privacy restrictions, leading to faster query development.\u003c/p\u003e\n"],["\u003cp\u003eSandbox data allows the use of \u003ccode\u003eSELECT *\u003c/code\u003e and running similar queries repeatedly, which is restricted with real data due to privacy checks.\u003c/p\u003e\n"],["\u003cp\u003eTo use sandbox data, queries must be limited to a specific date range (2018-08-18 to 2018-09-17) and use a designated sandbox customer ID.\u003c/p\u003e\n"],["\u003cp\u003eWhile the query development workflow is largely the same, sandbox data enables flexibility and speed by bypassing certain privacy limitations, leading to faster iterations and fewer errors.\u003c/p\u003e\n"]]],["The Ads Data Hub platform offers a synthetic dataset, or \"sandbox,\" for query development and experimentation, bypassing privacy checks. This allows for faster job runs, `SELECT *` usage for data inspection, and no difference checks. Sandbox use is recommended for iterating on draft queries and reducing privacy-related errors. Queries on sandbox data have specific parameters like an auto-updated date range and require selecting \"ADH Sandbox Customer.\" API users must use a specific sandbox account ID for their region.\n"],null,["As a tool to help you operate more effectively amidst privacy checks in Ads Data Hub, the platform includes a synthetic dataset. Unlike normal data, this dataset isn't subject to privacy checks, and as such should be used for experimentation and query development. The sandbox can improve your query development workflow by:\n\n- Running jobs faster. Because queries run on sandbox data aren't subject to privacy checks, your jobs will run faster.\n- Allowing you to inspect the underlying data. You can use `SELECT *` on sandbox data, giving you a better understanding of how your results could look.\n- Avoiding difference checks. Difference checks look at your query history, but aren't impacted by queries run on sandbox data. [Learn more about difference checks](/ads-data-hub/marketers/guides/privacy-checks#difference_checks)\n\nThese improvements allow you to iterate on draft queries faster and can reduce the frequency of errors due to privacy checks. As such, Ads Data Hub recommends that you use sandbox data to develop queries whenever possible.\n\nSandbox data and privacy restrictions\n\nBecause the sandbox data is synthetic, Ads Data Hub relaxes certain privacy restrictions. For example, the following actions are only possible when querying sandbox data:\n\n- Running queries using `SELECT *`.\n- Running a series of similar queries. This is a common practice for developing SQL queries, but doing so without using sandbox data makes it more likely that your jobs will run into privacy check issues. Jobs run on sandbox data won't impose data difference checks, allowing you to more rapidly iterate on SQL. [Learn more about privacy checks in\n Ads Data Hub](/ads-data-hub/marketers/guides/privacy-checks)\n\nSandbox query workflow\n\nThe workflow for developing queries that use sandbox data is nearly identical to developing queries that use your own data. The only differences are:\n\n- When querying sandbox data, you can write queries that use `SELECT *`.\n- The date range will be automatically updated to \"Aug 17 - Sep 18, 2018\" to match the contents of our sandbox data.\n- Sandbox jobs won't contribute to the execution history of your report.\n- To run queries on sandbox data, you must:\n - Run jobs from within the SQL editor of your report.\n - Select **ADH Sandbox Customer** from the **Ads data from** drop-down.\n- If you're using the API, you must use the specific sandbox account ID for your region:\n - `us`: '131148133'\n - `europe`: '548904246'\n - `asia-northeast1`: '811078775'\n - `australia-southeast1`: '448592203'\n\n[Learn more about writing and running queries in Ads Data Hub](/ads-data-hub/marketers/guides/run-queries)"]]
