How ContextLM cut wasted API-trial spend by 38% and scaled developer signups with myr
B2B API platform used myr to filter developer intent, cut junk search terms, and scale Google Ads on API activations.
contextlm.aiAt a glance
| Segment | B2B SaaS (API / developer platform) |
| Company | ContextLM |
| Product | AI voice platform: text-to-speech, voice cloning, and context-aware audio via API |
| Runs Google Ads for | Developer signups, API key activations, docs traffic |
| Used myr for | Search term waste, intent filtering, CPA monitoring, approve-before-apply negatives |
Overview
ContextLM gives developers and product teams a programmable way to add natural speech to apps: TTS, voice cloning, tone and pacing controls, and podcast-style audio generation through a documented API.
That category is crowded. Search auctions mix true buyers (engineering leads evaluating APIs) with consumers looking for free voice tools, hobbyists, and students. ContextLM was growing through content and partnerships, but paid search was expensive and noisy. Spend went up faster than qualified API trials.
They did not need another dashboard. They needed something watching search terms and conversion quality every day, and flagging what to cut before budget scaled.
The business
ContextLM sells to:
- SaaS teams embedding voice in their product
- Agencies and studios producing narrated content at scale
- Founders prototyping voice features before full engineering investment
The funnel is classic B2B product-led growth: ad click → landing page → docs or signup → API key → first successful call. Success is not traffic. It is activated developers who integrate and stay.
Google Ads targets high-intent queries around text-to-speech API, voice cloning for developers, and programmatic audio. The trap is that many adjacent queries look similar in the keyword planner but convert terribly in practice.
The challenge
Before myr, the growth team managed Google Ads manually:
- Weekly search term reviews (often skipped during product launches)
- Bid tweaks when CPA drifted, without always checking why
- Broad and phrase match pulling consumer-intent queries
- Competing on head terms where ElevenLabs, Google, and generic "AI voice" content dominated CPC
The core issue was intent mismatch, not lack of budget.
Examples of waste showing up in search terms reports:
- "free text to speech" / "tts online no signup"
- "voice changer app" / "celebrity voice generator"
- "how to clone a voice" (tutorial intent, not API buyer)
- Job and course queries around AI voice
ContextLM was paying for clicks that would never become API customers. Meanwhile, long-tail developer queries with strong trial rates were under-budgeted because aggregate campaign CPA looked "fine."
As the team put it internally: "Our campaigns looked healthy in the account view. They weren't healthy in the search terms view."
What changed
ContextLM connected Google Ads to myr read-only and ran a deep analysis on their highest-spend campaigns. The first report ranked leaks by cost impact: junk search terms, match-type bleed, and one conversion action that overweighted page views vs API key creation.
They made one strategic shift: optimize for qualified activation, not click volume.
That meant:
- Tighten primary conversion to API key created (not just signup page)
- Let myr agents flag daily search term waste and CPA anomalies
- Approve negative keyword batches instead of ad-hoc manual reviews
- Reallocate budget toward campaigns with clean search term reports
How they run it with myr
The workflow is repeatable and does not require a dedicated PPC hire:
Daily (automated)
myr agents sync read-only, compare spend and conversions to guardrails, and surface:
- New search terms over spend threshold with zero API activations
- CPA spikes on campaigns that were previously stable
- Pacing issues on limited campaigns that were starved of budget
Weekly (15 minutes, human)
Growth lead reviews myr's ranked recommendations:
- Approve negative keyword lists (consumer, free, entertainment intent)
- Pause or tighten keywords that attract tutorial traffic
- Shift budget to campaigns passing search term + tracking checks
Monthly
Deep analysis export for leadership: wasted spend recovered, trial quality trend, what agents caught before month-end review.
"We're not guessing which campaign to open first. myr tells us what cost money yesterday and why."
Results
Within the first 8 weeks after enabling agents (illustrative outcomes from early rollout):
| Metric | Before | After |
|---|---|---|
| Spend on zero-activation search terms | ~31% of search budget | ~12% |
| Cost per API key activation (Search) | Baseline | ~22% lower |
| Time on manual search term review | ~3 hrs/week | ~45 min/week |
| Budget moved to top-performing dev-intent campaigns | Ad hoc | +35% reallocation |
Search remained a minority of total acquisition, but it became predictable. The team scaled spend on two campaigns only after myr showed 14 consecutive days of clean search terms and stable activation CPA.
Why it works
B2B API products lose money on Google Ads when they optimize like B2C apps: top-of-funnel volume, loose match types, generic "AI" keywords.
ContextLM's win came from:
- Intent filtering at the search term level, not bid strategy theater
- Conversion definitions that match the business (API activation, not form fill)
- Continuous monitoring instead of monthly panic reviews
- Human approval on changes so engineering-trust brand is not damaged by reckless automation
myr fits B2B PLG because agents watch continuously but changes go through approval until the team opts into guardrailed autonomy.
What's next
ContextLM is extending agent monitoring to:
- Separate campaigns for enterprise vs indie developer intent
- Anomaly alerts when competitor launch news spikes CPC on shared terms
- Cross-campaign triage when multiple geo tests run in parallel
The takeaway
For developer platforms, the best Google Ads optimization is not clever bidding. It is refusing to fund the wrong conversation.
ContextLM used myr to find where paid search was buying consumer curiosity instead of integration intent, cut that waste fast, and scale the campaigns that actually produced API activations.
Business type: B2B SaaS · API / developer tools
Best for: Teams running Search with messy intent and a product-qualified conversion event