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.
Why use test accounts?
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.
Create test accounts and campaigns
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.
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.
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.
Create a few test campaigns under the test client account from the Google Ads page.
Take note of the client customer ID for the new test client account, and save it so you can make API calls later.
View test accounts
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.
Limitations
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.
[[["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-20 UTC."],[[["\u003cp\u003eTest accounts provide a risk-free environment to experiment with the Google Ads API and new configurations without affecting live campaigns or incurring charges.\u003c/p\u003e\n"],["\u003cp\u003eThey mirror the structure and functionality of production accounts, offering a realistic testing ground before deployment.\u003c/p\u003e\n"],["\u003cp\u003eTest accounts operate independently from production accounts, ensuring no interaction or impact on live data.\u003c/p\u003e\n"],["\u003cp\u003eThese accounts are accessible through the Google Ads UI and don't necessitate an approved developer token for initial API experimentation.\u003c/p\u003e\n"],["\u003cp\u003eWhile offering a robust testing platform, test accounts have limitations regarding serving metrics, certain features, and account hierarchy size.\u003c/p\u003e\n"]]],[],null,["\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nTest accounts let you try out new API implementations or account configurations\nprior to implementing the changes in your production environment.\n\nWhile production accounts serve ads that require billing and are rendered to\nusers, test accounts appear in the Google Ads UI as cancelled accounts since there\nis no active billing and they don't render ads to users.\n\nBecause test and production accounts cannot interact in any way, you cannot use\na test account under your existing production manager account. To use test\naccounts, you need a new account hierarchy, with a test manager account as the\nroot.\n\nWhy use test accounts?\n\nTest accounts don't affect your live ads or charge your account, hence they're a\nuseful way to experiment with the API. Test accounts provide extra benefits\nduring active development. Particularly, test accounts:\n\n- Can be set up in a hierarchy and organized just like production accounts.\n- Can be viewed and manipulated in the Google Ads UI, just like production accounts.\n- Don't require an approved developer token, so you can start experimenting with the API immediately, even before your application is reviewed or approved.\n- 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.\n- Have the same restrictions, including [rate\n limits](/google-ads/api/docs/best-practices/rate-limits), as production accounts.\n\nSince test accounts don't have budgets, you might see an error when creating a\ntest sub-account in a manager account. You can safely ignore this error.\n\nCreate test accounts and campaigns\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nThe following instructions create a test manager account, a test client account,\nand a few campaigns to populate the test client account. Note that \"client\" here\nrefers to a Google Ads client account, not your client app.\n\n1. Click the blue button to create a test manager account. If prompted, sign\n in with a [Google Account](//www.google.com/account/about/) that isn't\n linked to your production\n [Google Ads manager account](//ads.google.com/home/tools/manager-accounts/).\n There is also a link to create a new Google Account if you need to do so.\n\n [Create a test manager account](//ads.google.com/nav/selectaccount?sf=mt)\n2. While in your test manager account, create a test client account:\n Click **Accounts \\\u003e\n add_circle \\\u003e\n Create new account** and fill out the form. Any client accounts you\n create from your test manager account are automatically test accounts.\n\n3. Create a few test *campaigns* under the test client account from the Google Ads\n page.\n\n4. Take note of the **client customer ID** for the new test client account, and\n save it so you can make API calls later.\n\n| **Important:** Use the developer token of your *production* manager account when making requests against the *test* manager account. Even if it's not approved yet, the token still works on test accounts, including the ones just created.\n\nView test accounts\n\nTo view test accounts in the UI, you can\n[unhide the accounts](//support.google.com/google-ads/answer/7519830) by\nchoosing to view cancelled accounts.\n\nTest accounts appear with a red label:\n\nIf you don't see the red **Test account** label on your Google Ads account page,\nthen the account is a production account.\n\nLimitations\n\nTest accounts are a great option for testing changes before deploying them to\nproduction, or developing your application while your developer token has\n[test account access](/google-ads/api/docs/access-levels#access_levels_2). However, there are\nsome limitations to keep in mind.\n\n- 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.\n- 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.\n- Test manager account hierarchies can contain [up to 50](/google-ads/api/docs/best-practices/system-limits#account) test accounts.\n- Test accounts generating a high volume of continuous requests may be throttled without notice.\n\nTake a look at the\n[Testing Best Practices](/google-ads/api/docs/best-practices/testing#production-accounts)\npage for guidance on working around these limitations."]]