1
3 Comments

I spent €150 on Google Ads and got 0 installs. Here's what I'm doing instead.

I built a browser extension that helps creators find and reply to growing discussions on Threads. Called it ReThreads. Spent two months building it. Then realized I had zero users and zero distribution.

Google Ads seemed like the obvious move. Fastest way to get in front of people searching for "grow on Threads" or "Threads engagement." Set up three Search campaigns, €5/day, Maximize Clicks, about 30 keywords.

After 30 days and exactly €150 spent: 92 impressions, 4 clicks, 0 installs.

Not a single install from €150.

What went wrong? Search intent mismatch. People Googling "grow on Threads" want a strategy post or follower-boosting tips, not a tool. They're not looking for a browser extension. Also — the dev-heavy audience runs ad blockers, so they never even saw the ads.

I pivoted to zero-budget organic. Started posting on Twitter/X — 1 original post + 6 thoughtful replies per day. No product plugs. Just insights about timing, reply loops, and the Threads algorithm.

The results after 2+ weeks: actual conversations with potential users, people asking "what are you building?" without me bringing it up, and a growing sense of what early Threads creators actually need.

I wish I'd spent that €150 on building a following instead of building ad campaigns. For early-stage developer tools, community distribution beats paid acquisition every time. You can't buy attention when nobody knows your name exists.

on July 20, 2026
  1. 1

    Great insight. We actually tried that — our @ReThreads_app account got banned on Threads within days (automated flag, I think because the tool interacts with the platform). So we pivoted to using ReThreads on personal accounts and posting results from there. But you're right about the data angle — our detection system sees real-time patterns of what's gaining traction. A weekly "what's rising on Threads" post built from that data might work even better than self-promo. Thanks for the nudge.

  2. 1

    Your post-mortem is spot on, "grow on Threads" is informational intent, so a tool ad never had a chance. The thing I'd add, you're pivoting to X, but your actual users live on Threads, so I'd run the same organic playbook there and let the product generate the content, a weekly "what's actually working on Threads right now" post built from the reply/timing data ReThreads already sees. That turns the tool into a distribution engine (a data artifact people share) instead of a thing you have to describe, which is the one channel ad-blockers can't touch.

    I'm curious whether you've tried posting on Threads itself vs X, happy to compare notes on the data-as-distribution angle.

    1. 1

      Good catch — we're on Threads through personal accounts. The tool runs there, so working conversations and posting results from personal handles was the natural move. X is where build-in-public updates land, Threads is where the reply work happens. On the data-as-distribution angle: a weekly "what's rising on Threads" digest built from reply and timing patterns is next on the roadmap. What's your setup — happy to compare notes.