Untuk mendiskusikan dan memberikan masukan tentang produk kami, bergabunglah ke channel Discord Google Ads resmi di server Komunitas Iklan dan Pengukuran Google.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Opsi lain untuk membuat kredensial OAuth2 adalah dengan menggunakan OAuth2
Playground. OAuth2 Playground, bersama dengan Konsol Google API,
memungkinkan Anda membuat token OAuth2 secara manual.
OAuth2 Playground ditujukan bagi pengguna yang hanya perlu mengakses akun untuk
satu akun pengelola atau pengguna Google Ads. Jika Anda perlu meminta kredensial dari beberapa
pengguna, sebaiknya Konfigurasi library klien untuk
OAuth di Google Ads API.
Dari drop-down project, pilih project yang ada atau buat project baru.
Di halaman Credentials, pilih Create credentials, lalu pilih
OAuth client ID.
Di bagian Application type, pilih Web application.
Di bagian Authorized redirect URIs, tambahkan baris dengan:
https://developers.google.com/oauthplayground
Klik Buat.
Di halaman Client ID, catat client ID dan client secret.
Anda akan membutuhkannya di langkah berikutnya.
Jika memiliki project cloud yang sudah ada, Anda dapat menggunakannya kembali dengan menyetel
URI pengalihan yang sah seperti yang dijelaskan di langkah 5.
Membuat token
Buka OAuth2
Playground,
(menggunakan link ini akan mengisi otomatis beberapa nilai utama untuk Anda).
Klik ikon roda gigi
di sudut kanan atas dan pilih kotak berlabel Gunakan kredensial OAuth Anda sendiri (jika belum dipilih).
Pastikan:
OAuth flow ditetapkan ke Server-side.
Jenis akses disetel ke Offline (ini memastikan Anda mendapatkan
token refresh dan token akses, bukan hanya token akses).
Masukkan ID klien OAuth2 dan rahasia klien OAuth2 yang Anda dapatkan di atas.
Di bagian berlabel Langkah 1 - Pilih & otorisasi API, klik Google
Ads API dari daftar dan pilih cakupannya,
https://www.googleapis.com/auth/adwords. Kemudian, klik Otorisasi API:
Jika diminta, login ke akun yang ingin Anda beri akses dan otorisasi. Jika tidak, konfirmasi bahwa pengguna Google saat ini di sudut kanan atas adalah akun pengelola atau Google Ads yang ingin Anda peroleh kredensialnya.
Sebuah perintah akan muncul yang menunjukkan bahwa aplikasi Anda ingin
Mengelola Kampanye Google Ads Anda. Klik Setuju untuk melanjutkan.
Di tab berlabel Step 2 - Exchange authorization code for tokens,
Authorization code akan muncul. Klik
Exchange authorization code for tokens.
Jika semuanya berjalan lancar, Refresh token dan Access token akan
diisi untuk Anda (Anda mungkin harus meluaskan kembali
Langkah 2 - Tukarkan kode otorisasi dengan token):
Salin Refresh token ke dalam file konfigurasi untuk library klien pilihan Anda, bersama dengan client ID dan client secret.
Setelah memiliki token refresh, Anda tidak lagi memerlukan OAuth2 Playground
sebagai URI pengalihan yang sah. Untuk menghapusnya dari daftar URI pengalihan yang diizinkan:
Di halaman Kredensial, klik nama ID klien yang akan diedit.
Hapus https://developers.google.com/oauthplayground dari URI pengalihan yang sah. Perhatikan bahwa Anda harus membiarkan setidaknya satu URI pengalihan di tempatnya.
[null,null,["Terakhir diperbarui pada 2025-08-31 UTC."],[[["\u003cp\u003eThe OAuth2 Playground helps generate OAuth2 credentials for single Google Ads user accounts.\u003c/p\u003e\n"],["\u003cp\u003eYou need a web application client ID and client secret to use the OAuth2 Playground.\u003c/p\u003e\n"],["\u003cp\u003eThe process involves authorizing the Google Ads API and exchanging an authorization code for refresh and access tokens.\u003c/p\u003e\n"],["\u003cp\u003eAfter obtaining the refresh token, remove the OAuth2 Playground as an authorized redirect URI for security.\u003c/p\u003e\n"]]],[],null,["# OAuth Playground\n\nAnother option for generating OAuth2 credentials is to use the **OAuth2\nPlayground**. The OAuth2 Playground, in conjunction with the Google API Console,\nlets you manually create OAuth2 tokens.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nThe OAuth2 Playground is for users who only need to access the accounts for a\n*single* manager account or Google Ads user. If you need to prompt multiple\nusers for credentials, it is likely better to [Configure a client library for\nOAuth in the Google Ads API](/google-ads/api/docs/oauth/client-library).\n\nGet a client ID and client secret\n---------------------------------\n\n| **Warning:** To use the **OAuth2 Playground** , you need to generate a **client\n| ID** for a [web application](/identity/protocols/OAuth2WebServer). This is the *only* type of application that works with the OAuth2 Playground. Refer to [Select an app type](/google-ads/api/docs/oauth/cloud-project#select_an_app_type) for more information.\n\nIf you don't have an existing cloud project:\n\n1. Open the [Google API Console\n Credentials page](https://console.cloud.google.com/apis/credentials).\n\n2. From the project drop-down, select an existing project or create a new one.\n\n3. On the Credentials page, select **Create credentials** , then select\n **OAuth client ID**.\n\n4. Under **Application type** , choose **Web application**.\n\n5. Under **Authorized redirect URIs** , add a line with:\n `https://developers.google.com/oauthplayground`\n\n6. Click **Create**.\n\n7. On the Client ID page, take note of the **client ID** and **client secret**.\n You'll need these in the next step.\n\nIf you have an existing cloud project, you can reuse it by setting the\nAuthorized redirect URIs as described in step 5.\n\nGenerate tokens\n---------------\n\n| **Warning:** The Google user you're signed in as in your browser determines which Google Ads accounts you'll be able to access with the OAuth2 credentials you generate. Therefore, you may want to do these steps in an incognito window or when you're not signed in to your Google Account, since it's likely that the user whose credentials you want to use isn't the same user you were signed in as when you got the client ID and secret.\n\n1. Go to the [OAuth2\n Playground](/oauthplayground#step1&scopes=https%3A//www.googleapis.com/auth/adwords&url=https%3A//&content_type=application/json&http_method=GET&useDefaultOauthCred=checked&oauthEndpointSelect=Google&oauthAuthEndpointValue=https%3A//accounts.google.com/o/oauth2/v2/auth&oauthTokenEndpointValue=https%3A//oauth2.googleapis.com/token&includeCredentials=unchecked&accessTokenType=bearer&autoRefreshToken=unchecked&accessType=offline&forceAprovalPrompt=checked&response_type=code),\n (using this link should pre-populate some key values for you).\n\n2. Click the gear icon\n in the upper right corner and select the box labeled **Use your own OAuth\n credentials** (if it isn't already selected).\n\n3. Make sure that:\n\n - **OAuth flow** is set to **Server-side**.\n - **Access type** is set to **Offline** (this ensures you get a refresh token *and* an access token, instead of just an access token).\n4. Enter the **OAuth2 client ID** and **OAuth2 client secret** you obtained above.\n\n5. In the section labeled **Step 1 - Select \\& authorize APIs** , click **Google\n Ads API** from the list and select its scope,\n `https://www.googleapis.com/auth/adwords`. Then click **Authorize APIs**:\n\n6. If prompted, sign in to the account to which you want to grant access and\n authorization. Otherwise, confirm that the current Google user in the top\n right corner is the Google Ads or manager account for whom you want to obtain\n credentials.\n\n | If you got your client ID and secret only a few minutes ago, and you get an error such as **Error: redirect_uri_mismatch** , the changes you made may not have propagated. Click the back button in your browser, wait a few minutes, then try clicking **Authorize APIs** again.\n\n \u003cbr /\u003e\n\n | If you get an error that you have not been granted access by the developer and the app is currently being tested, you will need to visit the OAuth consent screen page within your GCP project and do one of the following:\n |\n | \u003cbr /\u003e\n |\n | - Publish the app.\n |\n | - Keep the app in the Testing status, and add yourself as a test user.\n |\n \u003cbr /\u003e\n\n7. A prompt appears indicating your app would like to\n **Manage your Google Ads Campaigns** . Click **Accept** to continue.\n\n8. In the tab labeled **Step 2 - Exchange authorization code for tokens** ,\n an **Authorization code** should appear. Click\n **Exchange authorization code for tokens**.\n\n9. If all goes well, the **Refresh token** and **Access token** should be\n filled in for you (you may have to re-expand\n **Step 2 - Exchange authorization code for tokens**):\n\n10. Copy the **Refresh token** into the configuration file for your client\n library of choice, along with the **client ID** and **client secret**.\n\n11. [Configure a client library for OAuth in the Google Ads API](/google-ads/api/docs/oauth/client-library).\n\nRemove the OAuth2 Playground from your client ID\n------------------------------------------------\n\nNow that you have a **refresh token**, you no longer need the OAuth2 Playground\nto be an authorized redirect URI. To remove it from the list of authorized\nredirect URIs:\n\n1. Go to the [Google API Console Credentials page](https://console.cloud.google.com/apis/credentials).\n\n2. From the project drop-down, select your project.\n\n3. On the Credentials page, click the **client ID name** to edit.\n\n4. Remove `https://developers.google.com/oauthplayground` from the **Authorized\n redirect URIs** . Note that you must leave at least *one* redirect URI in\n place.\n\n5. Click **Save**."]]
di sudut kanan atas dan pilih kotak berlabel Gunakan kredensial OAuth Anda sendiri (jika belum dipilih).
