Utilize sandbox data during your query development whenever possible. Jobs using sandbox data don’t introduce additional opportunities for differential privacy checks to filter your query results. Additionally, because of the lack of privacy checks, sandbox queries run faster, allowing for more rapid iteration during query development.
If you have to develop queries on your actual data (such as when using match tables), to make it less likely that you overlap rows, choose date ranges and other parameters which are unlikely to overlap for each iteration of your query. Finally, run your query over the desired range of data.
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 *. - When running queries on sandbox data, you must:
- Select start and end dates between 2018-08-18 00:00:00 and 2018-09-17 23:59:59.
- Select ADH Sandbox Customer from the Ads data from dropdown.
- If you're using the API, you must use the specific sandbox account ID for your region:
us: '131148133'europe: '548904246'asia-northeast1: '811078775'australia-southeast1: '448592203'
Learn more about writing and running reports.