We connect to one thing, on purpose.
A deliberately small surface — one OAuth into Google Ads, plus the operational connections required to run a SaaS. And a clean list of everything we don't touch. If you came here looking for an integrations marketplace, this is the wrong page on the wrong website.
What Lyra actually connects to.
Six connections. One does the work — Google Ads. Five run the company. Each one is named, scoped, and explained in plain language. Sub-labels are mono so you can scan; descriptions are sentences because trust isn't a checklist.
Google Ads
The only meaningful pipe in. You grant per-account access through Google's standard OAuth flow; we hold a refresh token and read campaign data on a schedule. Writes are off by default, opt-in per account, and reversible from the change-history feed inside the app.
↓ We read
- Campaigns, ad groups, ads
- Keywords + search-term reports
- Conversion data (incl. imported)
- Quality Score components
- Performance Max asset performance
- Bid history + change log
- Account-level budget pacing
↑ We write
- Bid adjustments
- Daily budgets
- Negative keywords
- Campaign + ad-group status
We don't download or store creative assets. We don't make campaign-level structural changes — we won't rename, restructure, or merge your campaigns. We don't create new campaigns, period. If a workflow would require any of those, the agent stops and asks you to do it.
Google Sub-MCC
Agency · readLets agency users link a manager account so all sub-accounts show up in Lyra without re-OAuthing each one. Cross-account feed and reporting; no write permissions at the manager level.
Stripe
Billing · webhooksHosted checkout for the trial signup, customer portal for plan changes and card updates, webhook events for trial-active / trial-end / payment state. Card numbers never touch our servers.
Anthropic Claude
LLM · outboundPrimary LLM for the Lyra Agent — recommendations, chat, pattern extraction, classification. Lyra-side API key. We pay for the AI; you pay for Lyra. User keys not supported, on purpose.
OpenAI
LLM · fallbackFallback LLM when Claude is unavailable, plus embeddings for similarity search via pgvector. Same arrangement: Lyra-side key, no bring-your-own.
Transactional email
Outbound · operationalSignup confirmations, trial-ending reminders (day 7 / 12 / 14), daily digests, password resets. Operational only — no marketing emails are sent through this channel.
That's the whole list.
No marketplace. No partner directory. No "supported integrations" tab in the dashboard. Six pipes, one of which actually touches your ad data, and we just told you which.
What Lyra doesn't connect to.
The bug in the old /integration/ page was listing GTM, GA4, and Slack as "integrations." None of them are. Here's the truthful list — every row is something a prospect or customer has asked us about, and every clarification is the actual reality.
We don't read or write container tags. If your conversion tracking lives in GTM, it ends up in Google Ads as a conversion — and we read it from there.
We never touch GA4 sessions, audiences, or events directly. GA4 conversions imported into Google Ads are visible to Lyra via the Google Ads API — that's the only path.
Google Ads only, on purpose. The product is built around one channel's quirks and we'd rather be excellent on one than mediocre on four.
Not connected today, not on the near roadmap. If you want SEO insight blended with paid, we're not your tool.
The AI provider is Lyra-side. Lyra pays for the AI; you pay for Lyra. Bring-your-own-keys is a different product shape and we're not building it.
There is no Lyra API for your team to integrate with. If a feature on a comparison page implied otherwise, the comparison page was wrong.
Soon, not yet.
Two things are scaffolded in the codebase but aren't shipped to customers. Listing them so you can plan, with no date attached. Every forward-looking item gets an IN STAGING chip — never a "Coming soon."
Slack notifications
Wired up in the backend, not yet exposed to customers. When it lands, it'll surface daily-digest summaries and trial-end alerts into a Slack channel of your choice. We're not promising a date because we don't have one.
Agency cross-account reporting
Recommendations feed is live across sub-accounts. Cross-account budget pacing and consolidated health scoring are in flight — usable in private beta, not in the marketing surface yet.
Security & data.
The exact rules for how OAuth tokens are stored, what leaves your account, where the database lives, and what happens when you delete. Short by design. Anything aspirational has been cut.
Encrypted at rest. Per-user, per-account.
OAuth refresh tokens live in Postgres, encrypted at rest. Each token is scoped to the user that granted it and the Google Ads account it was granted for — no shared keys, no global service accounts.
Revocable from Lyra settings, or directly from your Google accountRead-only by default. Writes are opt-in and logged.
Reads are scheduled and cached. Writes — bid changes, negative keywords, status flips — happen only when you've enabled auto-apply, are recorded in the customer-facing change history, and can be rolled back from there.
Every write · logged · reversible · attributableDatabase on Railway. AI calls go out from there.
Postgres + pgvector run on Railway. AI provider calls go to Anthropic and OpenAI. We don't ship customer data to any other vendor — no analytics warehouses, no enrichment services, no third-party CRMs.
Zero third-party data brokers in the chainCancel + delete. 30 days. Done.
When you cancel and request deletion, all OAuth tokens are revoked and account data is purged within 30 days. Stripe retains its customer record per its own retention policy — that's a Stripe concern, not ours, and we've separated it on purpose.
30 days · purge window · token revocation · immediate Run the audit.
Keep the findings.
Connect your account and let Lyra run its 18 tools for 14 days. If the projected waste recovery isn't worth at least 10× the $49, don't pay. You keep every insight either way.
Read-only connect · write access opt-in per tool · SOC 2 in progress · GDPR + CCPA compliant