75% of My Indie Game’s Pageviews Came From Threads: What 30 Days of GA4 Data Taught Me

After launching an indie game, one question becomes painfully important: how do people actually find it?

I’m building a browser game called ORA Quest and have been posting regularly on Threads. Likes and impressions were visible, but I didn’t know whether those posts were actually sending people to the game.

So I checked Google Analytics. The result was much more extreme than I expected.

594 pageviews in 30 days

From September 7 to October 6, 2026, the ORA Quest page recorded 594 pageviews and 407 users in GA4. It was by far the most-viewed destination on my site.

Threads accounted for 448 pageviews

GA4 split Threads traffic into two sources: l.threads.com / referral with 230 pageviews, and threads / social with 218.

Together that is 448 pageviews—about 75% of all ORA Quest pageviews.

For me, Threads was not a minor promotional channel. It was the main entrance to the game.

One platform can appear as multiple traffic sources

This was also a useful analytics lesson. If I had looked only at one Threads source, I would have badly underestimated its impact.

Referral data can be split depending on how a link is opened or attributed. On a small site, that matters a lot because every source can change the picture.

Google Search was almost invisible

Search Console told the opposite story. During the same period, the ORA Quest page itself received only 2 Google impressions and 0 clicks.

So the current path is not Search → ORA Quest. It is overwhelmingly Threads → ORA Quest.

That matches what I wrote earlier in I Released an Indie Game. Almost Nobody Found It Through Search.

This does not mean SEO is useless

Threads can bring visitors immediately, but posts disappear quickly in the feed. Search is weak for me today, yet a useful article can keep attracting people months later.

My current strategy is simple: use Threads to reach people now, and build search entrances for the future.

The hard part for a solo developer is getting the first 100 people

A game can be good and still be invisible. Large studios can buy reach; solo developers often cannot.

That makes social media especially useful early on. My numbers are one small case study: even when Google barely surfaced the game, Threads could still bring hundreds of visits.

Follower count is not the real metric

It is easy to obsess over followers, likes, impressions and replies. But for a game creator, the more important question is: did anyone reach the game?

A post with 10,000 impressions and zero game visits may be less valuable than a post with 1,000 impressions that sends 100 players.

I now care more about the full path: post → site → ORA Quest.

Is 594 pageviews a success?

Compared with a major web service, 594 is tiny. But at an early stage, the important part is not the absolute number. It is discovering a repeatable path that brings people in.

Knowing that roughly 75% came from Threads gives me something I can improve.

The next question is what visitors actually do

The next step is deeper than traffic: how long did they stay, did they start the game, did they finish the demo, and did they return?

That is how pageviews become real players.

Social media is not just promotion—it is part of the entrance

I now see Threads less as an advertising tool and more as part of the game’s discovery experience: see a post, open the profile, tap a link, launch the game, play.

That entire path can be designed and improved.

I want both social and search entrances

For now, Threads is the stronger short-term channel. At the same time, I’m documenting development problems and experiments so search can gradually become another source of discovery.

At the time of writing, about 75% of ORA Quest pageviews came from Threads. I want to keep tracking how that changes over time.

Play the free ORA Quest demo