Your own API access
Google Ads API access belongs to your own Cloud project, so its access level and daily quota are yours alone.
XerAds builds Google Ads campaigns from your media plan and pushes them straight into your own ad account. In the BYOK model you supply the OAuth client from your own Google Cloud project, where your Google Ads API access also lives, so nothing is routed through a shared XerAds account, the campaigns, the spend, and the data stay entirely yours.
Inside Ads Management · Google Ads
Your own ad account
Ads Management
Your API credentials
Setup check
Campaign
Awaiting your approval
-
Impressions
-
Clicks
-
Spend
In the BYOK model, XerAds never holds a credential that can touch your ad account. Your OAuth client and refresh token come from your own Google Cloud project, are encrypted at rest, and can be rotated or revoked by you at any time. Google Ads API access is granted to that same project, never to XerAds. Disconnecting removes our access without touching your live campaigns.
Google Ads API access belongs to your own Cloud project, so its access level and daily quota are yours alone.
With your own keys, every campaign is created paused, nothing serves or spends until you launch it.
With your own keys, revoke access at any time; your running campaigns are never altered.
Not every team wants to hold its own API keys. XerAds also runs Google App Campaigns as a managed service: we set up attribution and in-app analytics before launch, build and operate the campaigns across Search, Play Store, YouTube, and Display, then review performance with you every week. What changes is who does the work, the ad account, the spend, and the data stay yours in both models.
Book a free campaign auditBranch, Adjust, or Appsflyer set up and verified before a single rupiah is spent.
Campaigns built, launched, and optimised every week, with reporting that says what changed and why.
A managed engagement changes who operates the campaigns, never who owns them.
In the BYOK model, the agency administrator acts as the PIC: they hold the agency’s Google OAuth credentials, connect the agency-owned accounts, and operate campaigns. Agency staff can prepare briefs from media plans and see their own reports without ever handling a credential.
Credentials, connected accounts, and campaign operations sit with one named administrator.
Agency staff prepare briefs and read their own reports, and never handle a credential.
In the BYOK model, one set of agency credentials covers the whole team.
You stay the account owner throughout. XerAds is the software layer that turns a media plan into campaign structure, ads, and keywords, then writes them into the account you connected.

Build the strategic starting point in XerAds: objective, budget direction, audience, keywords, and creative guidance.
Paste the OAuth client ID and secret from your own Google Cloud project, enable the Google Ads API in that project, and pick the access level Google granted it. A built-in setup check tells you exactly what is missing.
Authorize XerAds against your own Google Ads account. Campaigns are always created paused first, so nothing spends before you review it.
Launch when you are happy with the build, then follow performance reporting pulled directly from your account.
With your own keys, you connect your own Google Ads account and XerAds is the software that builds the campaigns, you review and launch them yourself. With the managed option, our team runs your Google App Campaigns for you, including attribution setup, and reports back weekly. The ad account and the billing are yours in both cases; only the operator changes.
Yes, that is the whole point of the BYOK model. You supply the OAuth client from your own Google Cloud project, and XerAds writes campaigns into the account you connect. We never run your ads from a shared XerAds ad account: on the managed side too, our team works inside your account, not ours.
Three things: a Google Cloud project with an OAuth client, the Google Ads API enabled in that project with an access level granted (you apply for one in Google Ads API Overview in Cloud Console), and a Google Ads account to advertise from. The dashboard has a setup check that tells you which piece is missing and how to fix it. If you choose the managed option instead, you need none of them, we handle the setup.
Yes, against a Google Ads test account. Test access reaches test accounts only, so campaigns built with it will not serve real ads until Google grants your project Explorer, Basic, or Standard access. The setup check detects this and says so explicitly.
No. On the BYOK side every campaign is created paused, nothing serves or spends until you launch it yourself. On the managed side we launch only against the budget you approved in the brief, and any change to that budget is agreed with you first.
On the BYOK side we revoke our access token and stop reading your account. On the managed side, ending an engagement removes our operator access the same way. Either way your campaigns keep running exactly as they were, disconnecting never pauses or changes live advertising.
Technically no, but without it you only see Google’s own numbers, which tend to flatter the result. An independent attribution setup gives you a neutral read on which ads actually work. On managed engagements we set this up before launch and support Branch, Adjust, and Appsflyer, including auditing a setup you already have.
Performance is read back from your own Google Ads account, impressions, clicks, cost, conversions and conversion value, so the numbers in XerAds reconcile with the numbers in Google Ads, because they are the same numbers.
Create a workspace, complete a media plan, connect your own Google Ads account, and let XerAds build the campaign for you.
Start with your own keys