Skip to content

v0.13.1: Google Ads without a developer token, and Jev by TypeSafe

Choose a tag to compare

View all tags
@keysersoft keysersoft released this 27 Sep 08:49
· 38 commits to main since this release
v0.13.1
7769756
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Google Ads, without a developer token

A new Google Ads connector (#758) and a new Advertising category in the store. 17 read-only tools on the Google Ads API v25:

  • accounts you can open, their settings (currency, time zone, auto-tagging, optimization score) and the accounts under a manager (MCC);
  • campaign, ad group, ad and keyword performance for any date range, with Quality Score and its three components;
  • the search terms report, budget pacing with Search impression share lost to budget and to rank, conversion actions, change history (who changed what, and from which tool) and Google's recommendations;
  • any GAQL query with paging, and the field catalog to look fields up;
  • a playbook that maps the usual questions (account health, wasted spend, negative keywords, tracking audit, device, location and hour splits, landing pages, Performance Max, assets, audiences, MCC roll-ups) to the right tools and queries, at no API cost.

Setup is an OAuth client and one authorisation in the browser. Google retired developer tokens on 9 September 2026: API access now belongs to your Google Cloud project, and its Explorer access level already reads production accounts. The connector never writes to your account.

Verified live on two production accounts: every tool and every playbook query.

For adapter authors, docs/tool-definition.md now shows how to keep optional filters in a query-language string (GAQL, SOQL, JQL) with JSON-Schema defaults, with no engine change.

Jev by TypeSafe

A Jev connector (#757): pass evidence and a typed question, get back a yes/no probability, one option out of a set, or a position on ordered levels, each with its probabilities, in about 300 ms. Six tools, including a playbook on confidence gating. The REST engine now retries HTTP 529 ("overloaded"), and a bare Invalid request. from TypeSafe comes back with the valid question shapes.

Connectors: 259 → 261.

Fixes

  • Structured output with extra keys (#752): an inferred output schema was served as a closed object, so a response carrying one key more than the sample it was inferred from was rejected by the client. Search Console's dataState: "all" hit it; any REST tool could. Schemas are now served as open objects.

Cloud only

  • A daily trial report by mail for the operator (#753).
  • Sign-ups are attributed to a channel, and Google Ads gets a sign_up_verified conversion instead of counting raw form submits (#754).
Assets 2
Loading