This page is written for Google's API compliance reviewers. It states what EzBizi is, which Google Ads and Local Services data it reads, on whose behalf, and what it does not do.
| Legal entity | EZBIZI LLC |
|---|---|
| Address | 800 SE 4th Ave Ste 107, Hallandale Beach, FL 33009, United States |
| Website | www.ezbizi.com |
| Product | EzBizi — a field-service CRM, at app.ezbizi.com |
| API contact | development@ezbizi.com |
| Google Ads manager account | 706-109-4046 |
| Google Cloud project | ezbizi-506117 (number 247590132639) |
EzBizi is sold as a monthly software subscription to service businesses — home services, trades, and multi-location franchises. They use it to manage customers, jobs, scheduling, inspections, staff and billing in one system.
Revenue comes entirely from those subscriptions. EzBizi does not resell advertising, take a percentage of ad spend, manage campaigns as a service, or monetise data in any form. Google Ads API access exists for one purpose: to bring a customer's own advertising results into that customer's own CRM record.
The Leads module inside EzBizi. Its purpose is to close the gap between an advertising enquiry and the work that results from it.
A service business receives enquiries through Google Local Services Ads. Those enquiries live in Google's interface, while the resulting customer, job, invoice and technician assignment live in the CRM. Nobody can answer "what did this lead actually become?" without cross-checking two systems by hand.
The Leads module retrieves each customer's own Local Services lead and conversation data, plus their Google Ads reporting metrics, and shows them beside that business's existing records. An enquiry becomes a customer and a job in the same system, with the originating source preserved so the work can be attributed back to the advertising that produced it.
Every user reaches the data through their own EzBizi login, governed by role-based permissions inside their own organization. It is not offered as a general-purpose Google Ads management tool and Google Ads data is never shown to anyone other than the account owner's own staff.
EzBizi is a multi-tenant platform. Each customer authorizes their own Google Ads account through a standard OAuth 2.0 authorization-code flow against EzBizi's own registered OAuth client. There is no shared credential, no manager-level access to accounts we were not granted, and no scraping of any kind.
| 1 | A signed-in EzBizi user opens the Leads tab and chooses Connect Google Ads. |
|---|---|
| 2 | They are sent to Google's consent screen, branded EZBIZI LLC, requesting the adwords scope with offline access. |
| 3 | They grant or decline. Declining changes nothing. |
| 4 | EzBizi exchanges the code, encrypts the refresh token, and stores it scoped to that customer alone. |
| 5 | The accounts the customer has granted are listed, and they choose which to link. |
| 6 | Scheduled synchronisation retrieves that customer's leads and reporting on their behalf. |
| 7 | They may disconnect at any time, which deletes the stored grant. |
Offline access is requested because synchronisation runs on a schedule rather than only while somebody is watching the screen.
| Service | Purpose | Operation |
|---|---|---|
| Local Services API — detailed lead reports | Retrieve the customer's own LSA leads, type, category and charge status | Read |
| Local Services API — lead conversations | Show the enquiry's message and call history on the lead record | Read |
Google Ads API — customer, customer_client | List the accounts the customer has granted, so they can choose | Read |
Google Ads API — campaign metrics via GoogleAdsService.Search | Spend, impressions and lead volume for the customer's own reporting | Read |
| Local Services API — lead status | Apply an explicit user action, such as marking a lead booked or archived | Write |
Usage is predominantly read. The single write path is lead status, and it is always the direct result of a person acting in the EzBizi interface — marking a lead as booked when they schedule the job, for example. Every such call is recorded in that organization's audit log with the acting user, timestamp and target.
EzBizi does not create, modify or pause campaigns; set or adjust bids or budgets; manage keywords, assets or creatives; or perform automated bulk mutation of any kind.
The Google Ads API publishes exactly one OAuth scope,
https://www.googleapis.com/auth/adwords. There is no read-only variant, so requesting
it is the only way to read a customer's own lead and reporting data.
Per-customer isolation. Every stored record carries its owning organization. Reads are filtered and writes are stamped and verified at the data layer; cross-organization writes are refused outright.
Token storage. Refresh tokens are encrypted at rest with application-level encryption, masked on every serialisation, and are not retrievable through any API response or support view.
No client-side credentials. The OAuth client secret and all tokens remain server-side. Redirect URIs are derived from the application's own configured origin, never from request input.
No aggregation, no resale. Data retrieved for one customer is never combined with another's, sold, shared with third parties, or used to train models.
Revocation. Disconnecting deletes the stored grant. Customers may also revoke access in their Google Account, which EzBizi detects and surfaces as a broken connection rather than failing silently.
Audit. Connection, disconnection and every write are recorded with the acting user and a timestamp.
EZBIZI LLC accepts the Google Ads API Terms and Conditions and the Required Minimum Functionality expectations. The tool is used exclusively by the businesses that own the connected accounts, to view and act on their own advertising results.