Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://developers.google.com/google-ads/api/docs/best-practices/test-accounts below:

Test accounts | Google Ads API

Stay organized with collections Save and categorize content based on your preferences.

Test accounts let you try out new API implementations or account configurations prior to implementing the changes in your production environment.

While production accounts serve ads that require billing and are rendered to users, test accounts appear in the Google Ads UI as cancelled accounts since there is no active billing and they don't render ads to users.

Because test and production accounts cannot interact in any way, you cannot use a test account under your existing production manager account. To use test accounts, you need a new account hierarchy, with a test manager account as the root.

Test accounts don't affect your live ads or charge your account, hence they're a useful way to experiment with the API. Test accounts provide extra benefits during active development. Particularly, test accounts:

• Can be set up in a hierarchy and organized just like production accounts.
• Can be viewed and manipulated in the Google Ads UI, just like production accounts.
• Don't require an approved developer token, so you can start experimenting with the API immediately, even before your application is reviewed or approved.
• Can't serve ads or interact with your production accounts in any way. This gives you a safe environment to test code or configuration changes without impacting your serving accounts.
• Have the same restrictions, including rate limits, as production accounts.

Since test accounts don't have budgets, you might see an error when creating a test sub-account in a manager account. You can safely ignore this error.

The following instructions create a test manager account, a test client account, and a few campaigns to populate the test client account. Note that "client" here refers to a Google Ads client account, not your client app.

1. Click the blue button to create a test manager account. If prompted, sign in with a Google Account that isn't linked to your production Google Ads manager account. There is also a link to create a new Google Account if you need to do so.

   Create a test manager account

2. While in your test manager account, create a test client account: Click Accounts > add_circle > Create new account and fill out the form. Any client accounts you create from your test manager account are automatically test accounts.

3. Create a few test campaigns under the test client account from the Google Ads page.

4. Take note of the client customer ID for the new test client account, and save it so you can make API calls later.

To view test accounts in the UI, you can unhide the accounts by choosing to view cancelled accounts.

Test accounts appear with a red label:

If you don't see the red Test account label on your Google Ads account page, then the account is a production account.

Test accounts are a great option for testing changes before deploying them to production, or developing your application while your developer token has test account access. However, there are some limitations to keep in mind.

• Because test accounts can't serve ads or interact with your production accounts in any way, serving metrics -- like impressions, conversions, or cost data -- are empty.
• Some features cannot be tested with test accounts. This includes bid simulations, conversion uploads, and billing. Other features, including recommendations, have limited capabilities within test accounts because test accounts don't generate serving data.
• Test manager account hierarchies can contain up to 50 test accounts.
• Test accounts generating a high volume of continuous requests may be throttled without notice.

Take a look at the Testing Best Practices page for guidance on working around these limitations.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-18 UTC.

[[["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 2025-08-18 UTC."],[[["Test accounts provide a risk-free environment to experiment with the Google Ads API and new configurations without affecting live campaigns or incurring charges."],["They mirror the structure and functionality of production accounts, offering a realistic testing ground before deployment."],["Test accounts operate independently from production accounts, ensuring no interaction or impact on live data."],["These accounts are accessible through the Google Ads UI and don't necessitate an approved developer token for initial API experimentation."],["While offering a robust testing platform, test accounts have limitations regarding serving metrics, certain features, and account hierarchy size."]]],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4