A local business Orange trusts
One tech. Tools and parts. Done today.

Tool name: internal Python automation (no public name, no UI exposed to third parties).
Operator: ExpressCare Solutions LLC (sole owner: Alexey Semenov).
Google Ads account: a single CID owned by ExpressCare Solutions LLC, used exclusively to advertise our own appliance-repair service in Orange, Irvine, Tustin, Santa Ana, Anaheim, Costa Mesa.
Access tier requested: Basic Access.
End-users of the tool: the owner only. No customers, partners, or third parties access the API or its data.

What the integration does

The integration is a server-side Python script that runs on our internal infrastructure (the same Django server that powers this website). It performs three concrete workflows against our own Google Ads account:

1. Offline conversion upload (write).

• Service: ConversionUploadService.UploadClickConversions.
• Trigger: a customer submits a booking on this website (POST /book/) or the contact form (POST /contact-form/), or clicks a tel: link. The Django view writes the lead to our PostgreSQL DB and, in the same background thread, queues a conversion event.
• Payload: gclid (captured from the URL at landing time and stored in a first-party cookie for up to 90 days — see Privacy Policy §1), conversion action resource name, conversion date/time, conversion value (the quoted job amount, when known), currency (USD).
• Purpose: tell Google Ads which clicks led to real booked jobs so Smart Bidding can optimize toward profitable keywords instead of just form-fills.

2. Campaign performance reporting (read).

• Service: GoogleAdsService.SearchStream with GAQL queries against campaign, ad_group, keyword_view, and geographic_view resources.
• Cadence: daily cron job at 06:00 PT pulls yesterday's metrics (impressions, clicks, cost_micros, conversions, conversions_value, ctr, average_cpc) for the last 30 days.
• Output: a CSV stored on our server and a simple HTML dashboard the owner reviews each morning. No data leaves our infrastructure.
• Purpose: identify under-performing keywords and over-performing geos for the next manual optimization cycle.

3. Programmatic bid & negative-keyword updates (write, limited).

• Services: CampaignCriterionService.MutateCampaignCriteria (add negative keywords surfaced by the reporting workflow above), AdGroupBidModifierService.MutateAdGroupBidModifiers (adjust bid modifiers by ZIP code based on per-geo CPA).
• Frequency: at most once per week, owner-initiated, with a dry-run mode that prints the intended mutations before execution.
• Scope: never touches budgets above the daily cap set manually in the Google Ads UI; never creates or pauses campaigns.

What the integration does NOT do

• It is not a SaaS product. No external customer logs in, signs up, or pays for access.
• It does not read, manage, or report on Google Ads accounts other than the single CID owned by ExpressCare Solutions LLC.
• It does not resell API access, white-label it, or expose its functionality through any third-party interface.
• It does not store or transmit Google Ads data outside of ExpressCare Solutions LLC's own server.
• It does not use Customer Match, audience uploads, or any feature that requires hashed PII upload.

Authentication & security

OAuth 2.0 with a refresh token tied to info@onevisitrepair.com (the owner's verified company Google account). The developer token is stored in a server environment variable, never committed to source control, and not shared with any third party. All API calls are made server-to-server; the browser never sees an API credential.

The data flows above are also described from the user's perspective in our Privacy Policy (sections 1, 2, and 3).