How we connect to Google Ads.
Written for anyone reviewing this app, in plain language: what TreeLeads is, why it needs access to a Google Ads account, and exactly where that access starts and stops.
1. What TreeLeads is
TreeLeads is software sold to tree service companies — the businesses that remove storm-damaged oaks, trim canopies and grind stumps. A tree company's advertising problem is specific: the work is urgent, the customer searches on a phone while looking at the damage, and the company that answers first usually gets the job.
The software runs that path end to end. It operates the Google Search campaigns, the booking page the ad points at, the tracking and transcription of the calls those ads produce, the follow-up when nobody answers, and the report that ties a booked job back to the keyword that caused it.
Customers buy it three ways: the software on its own, a course that teaches them to run it themselves, or an engagement where we run the advertising for them. All three are described on the pricing page.
2. Why it needs Google Ads access
The product's entire promise is connecting money spent to jobs booked. That sentence cannot be delivered without reading the spend.
- To report. A customer needs to see what each campaign, ad group and keyword cost, and what it produced. That comes from the Google Ads API and nowhere else — a screenshot pasted into a monthly PDF is what we are replacing.
- To join the two halves. A call arrives, gets transcribed, and becomes a booked estimate. Attribution is what connects that booked estimate back to the click that caused it. Without Ads data the second half of the sentence is missing.
- To act, where asked. For customers on a managed engagement, we also change the account — pause a keyword that is burning budget, shift spend to the campaign that is producing, or activate a prepared storm campaign after a severe-weather alert. Doing that by hand across accounts is how money leaks.
Access is per account and per customer. A customer authorises the specific Google Ads account they want connected, at Google's own consent screen, and nothing else.
3. Exactly what we access
| What | Read or write | What it is used for |
|---|---|---|
| Campaigns, ad groups, ads, keywords | Read — and write on managed accounts | Report structure and performance; pause, adjust or launch on a managed account at the customer's instruction. |
| Budgets and bids | Read — and write on managed accounts | Show what is being spent; move spend between campaigns that are and are not working. |
| Cost, impression and click metrics | Read | The cost side of the cost-per-booked-job figure. |
| Conversion actions and conversion data | Read, and upload conversions | Tie a booked job or a tracked call back to the click that produced it, so the account optimises toward jobs rather than clicks. |
| Account and billing identifiers | Read | Confirm the right account is connected and label reporting correctly. |
| Google Analytics 4 measurement | Read | Page and conversion measurement for the advertising pages we operate. |
| Google Tag Manager container | Configuration | Deploy and maintain conversion tracking on those pages without hand-editing page code. |
We request the narrowest access that makes the above work. Where a customer only wants reporting, the connection stays read-only.
4. What we never do with it
- We never sell Google user data.
- We never transfer it to another app or third party, except as necessary to provide the features the customer is using, to comply with law, or in a merger where the receiving party stays bound by the same commitments.
- We never use it for advertising — not to build audiences, not to target anyone, not for our own marketing. The only advertising it touches is the customer's own account, at their instruction.
- We never let a human read it except with the customer's explicit consent for something they asked for, where it is necessary for security, or where the law requires it.
- We never pool one customer's Google data with another's. Territory exclusivity is the commercial promise of this company; mixing account data would break it.
The full detail, including storage location, retention and who inside the company can see what, is in section 4 of the privacy policy.
5. How the connection is made
- 01
The customer starts it
The connection is initiated by the customer, from their own account. We never connect an account without the owner doing this.
- 02
Google's consent screen
Google shows what is being requested and who is requesting it. The customer approves or declines there — not here.
- 03
We store a token, not a password
We receive an OAuth token. We never see or store a Google password. The token is encrypted at rest, never written into a browser bundle, a log line or a URL.
- 04
It can be ended at any time
From Google Account permissions, or by emailing us. Revocation is immediate and does not require our cooperation.
6. How a customer disconnects
- Open Google Account permissions.
- Select {{brandName}}.
- Choose Remove access. Access stops immediately.
We delete the stored token within 30 days. To also delete the reporting data already pulled, email support@treeleads.io — revoking access tells Google to stop us, but it does not tell us to erase history, so we treat that as a separate, explicit instruction. Step-by-step on the data deletion page.
7. Questions about this integration
Email support@treeleads.io or call (469) 369-2430. If you are reviewing this application on behalf of Google and need something this page does not answer, say so in the subject line and it will be answered the same day.