How Privlekai uses the Google Ads API
A full description of our business model, our users and our use case for the Google Ads API, including our coverage of Required Minimum Functionality.
1. What Privlekai is
Privlekai is a self-service advertising tool for owners of very small businesses in Kazakhstan — a window repair company, a dental clinic, a driving school, a furniture workshop. These businesses have an advertising budget in the range of 50 000 – 300 000 ₸ per month (roughly USD 100 – 600). No agency will take them on at that size, and the Google Ads interface assumes knowledge they do not have and will not acquire.
Privlekai does the work an account manager would do, in the customer's own Google Ads account, and — this is the part that matters for this audience — explains every decision in ordinary language, including what each decision costs them. The customer reviews and confirms; Privlekai never acts on money by itself.
The interface is shown screen by screen on the product tour.
2. Who uses it
- Users of the tool
- External users — third-party businesses that are not us and are not related to us. Each is the owner of the Google Ads account it connects.
- Market
- Kazakhstan, initially Almaty and Astana. Interface in Russian and English; ads in Russian and Kazakh.
- Typical user
- The owner of the business, not a marketing employee. Usually advertising for the first time. In most cases has never opened Google Ads before.
- Number of accounts
- One Google Ads account per business. Pilot scale at launch is a small group of businesses; we are not building a bulk-management platform for agencies.
3. Tool classification
- Tool type
- Full-service tool — it creates, manages and reports.
- Users
- External users.
- Campaign types
- Search. Other campaign types are out of scope for the first release.
- Functionality
- Creation · Management · Reporting · Keyword Planning.
- Third-party tool used
- None. Privlekai is developed by us; we do not resell or rebrand anyone else's tool.
- App conversion tracking
- Not used.
4. What we do with the API
Every operation below is triggered by an action the business owner took in Privlekai's interface. Nothing is done on a schedule that the owner has not agreed to, and nothing that spends money happens without an explicit confirmation.
| What the user does | What Privlekai does for them | Google Ads API services |
|---|---|---|
| Asks whether advertising is worth it | Finds the terms their customers actually search for, retrieves search volume, competition and top-of-page bid estimates, and forecasts what a given budget would produce. Returns a plain answer, including a recommendation not to advertise where that is the honest one. | KeywordPlanIdeaService, KeywordPlanService, GeoTargetConstantService |
| Approves a proposed campaign | Creates a Search campaign with geographic and language targeting, a daily budget, a bidding strategy, ad groups, keywords with match types, campaign negative keywords, responsive search ads, callout extensions and a conversion action. | CampaignBudgetService, CampaignService, CampaignCriterionService, AdGroupService, AdGroupCriterionService, AdGroupAdService, AssetService, CampaignAssetService, ConversionActionService |
| Runs the campaign | Pauses, resumes and removes campaigns, ad groups, ads and keywords; edits budgets, bidding strategies, targeting and schedules; adds negative keywords found in wasteful search terms. Each change is logged with its reason and, where it affects spend, with the person who approved it. | The same mutate services as above |
| Asks how it is going | Reports impressions, clicks, cost and conversions at account, campaign, ad group, ad, keyword and search term level, with status and average CPC, and ends the report with a recommendation. | GoogleAdsService.SearchStream over customer, campaign, ad_group, ad_group_ad, keyword_view, search_term_view |
| Connects an account | Lists the Google Ads accounts the signed-in user can access, so they can pick the right one. | CustomerService.ListAccessibleCustomers, GoogleAdsService.SearchStream over customer_client |
5. Required Minimum Functionality
Privlekai is a full-service tool, so Creation, Management and Reporting RMF all apply to it. The table below states where each requirement is met in the interface. Screen numbers refer to the product tour.
Creation
| Requirement | Where in Privlekai | |
|---|---|---|
| Create a Search campaign with geographic and language targeting | Yes | Screen 2 — locations, radius, presence setting and languages are proposed and editable |
| Conversion tracking — website or call | Yes | Screens 2 and 3 — a conversion action is created; calls from ads are tracked by default, website conversions once the tag is installed |
| Ad group and keyword management with match types | Yes | Screens 2 and 4 — ad groups and keywords with exact, phrase and broad match, editable and removable |
| Campaign negative keywords | Yes | Screens 2 and 4 — proposed at creation, and added from wasteful search terms during management |
| Bidding strategies: Maximize Conversions, Target CPA, Target ROAS | Yes | Screen 2 — chosen and explained; the target is set from the account's own data once it exists |
| Budget configuration | Yes | Screens 2 and 4 — daily budget shown in monthly terms, editable at any time |
| Callout extensions | Yes | Screen 2 — callout assets generated and attached to the campaign |
Management
| Requirement | Where in Privlekai | |
|---|---|---|
| Edit campaign settings | Yes | Screen 4 — targeting, schedule, networks and name |
| Pause, enable and remove campaigns, ads and keywords | Yes | Screen 4 — status controls at every level |
| Modify bidding options | Yes | Screen 4 — bidding strategy and target |
| Adjust budgets | Yes | Screen 4 — budget editable, with the effect on expected volume stated |
Reporting
| Level | Metrics shown | |
|---|---|---|
| Account | Yes | Impressions, clicks, cost, conversions |
| Campaign | Yes | The same, plus status |
| Ad group and ads | Yes | Impressions, clicks, cost, conversions, status |
| Keywords | Yes | Impressions, clicks, cost, conversions, average CPC, status |
| Search terms | Yes | Search term, matched keyword, match type, cost, conversions |
6. Account access and ownership
- Each business connects its own Google Ads account through Google's official OAuth consent flow. We ask for the
adwordsscope and nothing else. - The account stays the customer's. We do not require businesses to move their account under a manager account we control, and we do not become an administrator of their account.
- Access is revocable by the customer at any time, from inside Privlekai or from their own Google Account security settings. Revocation stops all Privlekai activity in that account immediately.
- Our manager account exists for API access only. Customer accounts are not linked beneath it, and no budget flows through it.
- Refresh tokens are encrypted at rest, bound to the tenant they belong to, and are never shared between customers or exported.
- Every API call that changes something is written to an action log that records what changed, why, and which person approved it. The log is visible to the customer.
7. Money — who pays whom
- The business pays Google directly, from its own Google Ads account with its own payment method. Privlekai never receives, holds, forwards or spends a customer's advertising budget.
- Privlekai takes no percentage of advertising spend. We charge a subscription for the software. A model paid as a share of spend rewards a provider for spending more of a customer's money, which is exactly wrong for a business advertising on 100 000 ₸ a month.
- We do not resell advertising, do not act as a media buying agency and do not mark up Google's prices.
8. Data handling and disclosures
- Reporting freshness. Google Ads performance data is retrieved from the API when the customer opens a report and is never more than 24 hours old. Where Google has not yet finalised a figure, we say so instead of showing a number that will change.
- Separation from non-Google data. Google Ads data is always reported separately from data of any other advertising platform. We do not merge them into a single blended metric.
- Whose data is whose. A customer sees only the data of the accounts they connected. Data is isolated per tenant at the database level.
- No resale of data. We do not sell, license or otherwise pass customer advertising data to third parties, and we do not use one customer's account data to advantage another.
- Aggregate benchmarks, when we show how a business compares to similar businesses, are anonymised and only shown above a minimum group size, so that no individual advertiser can be identified.
- Deletion. A customer can disconnect an account and request deletion of the data we hold for it. Details are in the privacy policy.
9. Other advertising platforms
Privlekai is being built to work with Meta (Facebook and Instagram) as a second, separate advertising channel, for businesses whose customers are not searching for what they sell. Choosing between channels — and saying openly when Google Search is the wrong one — is part of the product's value.
Where a business runs both, Google Ads figures are presented on their own, labelled as Google Ads, and are never combined with figures from another platform into one number. Any comparison between channels is shown as a comparison, with each side's numbers stated separately.
10. Business model
The business owner pays for Privlekai as software. The unit of pricing is a connected advertising channel — one platform in one advertising account — with the second and subsequent channels priced lower than the first, because they cost us less to serve. Customers pay only for the months in which they actually advertise, since much of this audience is seasonal.
There is a free tier covering everything the software does without AI reasoning, plus one complete campaign, once. There is a one-off purchase — a single campaign plus one month of management, without a subscription — for businesses that advertise twice a year and will never subscribe. Payments are collected in Kazakhstan through local acquiring. Final prices will be published before launch.
Revenue therefore comes entirely from the businesses using the tool. It does not come from advertising spend, from Google, or from selling data.
11. Current status
Privlekai is in development, built by an independent developer in Kazakhstan.
- The product design is complete and documented, including the Google Ads campaign structure, the reasoning the tool must present, and its compliance checks.
- The Google Ads manager account, the Google Cloud project with the Google Ads API enabled, and the OAuth consent screen are configured and published.
- The interface is at the design stage: the product tour shows mock-ups, not screenshots of shipped software.
- The first release covers Google Ads Search campaigns for a small group of pilot businesses in Kazakhstan.
We publish this page rather than a marketing claim because a tool that will operate in other people's advertising accounts should be inspectable before it is usable. If anything here is unclear or looks wrong, we would rather be told.
12. Contact
- Developer
- Sergey Plotnikov, independent software developer
- Location
- Almaty, Kazakhstan
- softispower@gmail.com — read every day, including for anything related to the Google Ads API
- Website
- https://privlek.ai