Hi Priscila — the detail that settles this is in your error: SC424 wrapping “[401] The provided client secret is invalid” (invalid_client), and the client_id in that callback (408604349651-…) is Make’s own shared OAuth app for google-ads2, not anything from your account. You used the default connection, so Make’s shared client secret for Google Ads on us2 is stale/revoked on Google’s side. Nothing you reauthorize with default settings can fix that — only Make rotating their secret can.
One 2-minute check before you build anything: create the default connection once more, fresh (incognito window). If it suddenly goes through, Make already rotated the secret and you’re done. If you get the same SC424 with the same client_id, it’s confirmed still broken and the custom client below is justified.
1. In Google Cloud Console, create (or pick) a project and enable the Google Ads API under APIs & Services > Library.
2. Under APIs & Services > OAuth consent screen, set the user type to External and publish the app (status: In production). Left in Testing, Google kills the refresh token after 7 days and this connection breaks again next week. If you later see a “Google hasn’t verified this app” warning while authorizing, that’s your own app — choose Advanced > continue.
3. Under Credentials, create an OAuth client ID (Web application) and add this exact Authorized redirect URI — the callback from your own error page: https://us2.make.com/oauth/cb/google-ads2
4. In Make, add a new Google Ads Campaign Management connection, open Show advanced settings, and paste your Client ID and Client Secret. (Make requests the scope — https://www.googleapis.com/auth/adwords — itself; there’s nowhere you need to type it.)
5. Make’s advanced settings for this app also take a developer token. It’s in your Google Ads manager account under Tools > API Center. Paste that in, then authorize with the Google login that has access to the ad accounts.
6. Verify before switching anything: run a single module on its own for yesterday, then compare the cost/click totals against the Google Ads interface for the same account and day (check the account timezone matches). If they match, point the daily scenario at the new connection and re-run the missing days from 27 Oct — first check that your storage step keys rows by date, so the backfill overwrites instead of duplicating.
The one alternative cause to be ready for: if your developer token is still at Test access, the new connection will authorize fine but the data calls will then fail with a developer-token error. That is a different failure from this 401 — it means the OAuth fix worked and the remaining wait is Google’s Basic access approval, which takes days, so it’s worth applying for now rather than after.
Quick question that decides your timeline: in your manager account’s API Center, does your developer token show Basic access already, or Test?