01 / THE SIGNAL

我们发现了什么

Show HN:Revliu——从获客到收入的多触点归因。如今,Revliu 可跟踪获客来源、回访访客、会话、触点和收入。

  • 来源:Hacker News(发现于 2026-09-10)
  • 证据等级:D · 发现产品或需求信号,暂未获得可核验的商业证据。
  • 商业模式:Subscription SaaS
  • 主题:营销与增长
  • 初筛评分:24.2/100 · 收录 1 次
#增长工具#待验证#产品发现
02 / SOURCE & EVIDENCE

证据,比故事更重要。

发现产品或需求信号,暂未获得可核验的商业证据。

规则清洗与初筛,未经人工商业核验。原文语境、实际客户和付费情况仍需自行验证。

引用与数字披露

来源类型(原作者自述/第三方测算/媒体转引)需采集端标注,本版尚未落字段。

短句引用
作者
未标注
抓取日期
来源类型
未标注
数字口径
币种
未标注
口径
未标注
披露主体
未标注
披露日期
未标注

中文辅助译文(来源摘要)

我是一名创始人,刚刚打造了 Revliu。在打造过几款产品之后,我一直想弄清楚我的客户究竟是如何找到我的。哪个推广活动带来了他们,他们来自哪个来源,以及他们的完整旅程是什么样的。市面上已经有这类工具,但我反复遇到的一个问题是,它们往往只停留在首次触点或末次触点上。这就是为什么我围绕多触点归因和完整的客户旅程来构建 Revliu。一旦有人访问你的网站,Revliu 就会为他们分配一个匿名 ID 并开始追踪他们的旅程。一旦他们注册,这个旅程就可以关联到真实的客户。从那里,你可以看到他们是否处于试用阶段,他们多久回来一次,打开了多少次会话,以及最终他们何时付费。对我来说,这也让我更容易与该用户交流,了解他们为什么在那个特定时刻决定继续推进。如今,Revliu 可以追踪获客来源、回访访客、会话、触点以及收入。我不想仅仅知道某个推广活动获得了一定数量的展示量,我想知道它究竟带来了多少收入。展示量并不是我真正关心的。应用本身相当简洁。主页面为你提供按来源划分的收入概览。流量页面展示访客、他们的旅程以及他们的会话。推广页面展示获客漏斗。对于 SaaS 来说,这可以是访客 → 潜在客户 → 试用 → 付费客户。对于在线商店来说,这可以简单地是获客 → 购买。客户页面让你可以单独查看每个客户,查看他们的触点、他们来自哪里、他们的旅程以及他们何时购买。在原理上,技术层面很简单。它从一个获得 ID 的匿名访客开始。我们追踪他们的访问和触点。当他们注册时,那段匿名旅程就会关联到该客户。Stripe 也已接入,所以当客户付费时,收入就可以关联回同一段旅程。

目标基本上是连接 获客 → 访问 → 注册 → 客户 → 收入。目前,这款应用仍处于第一阶段。我还没有构建我想要的所有集成。我接下来想构建的是一些不仅仅展示数据的功能。如果有人留下了邮箱但从未完成注册,多次回访但没有购买,或者表现出真正的兴趣却没有转化,我想利用这些信息来尝试挽回那位潜在客户。其思路是通过电子邮件再次触达他们,或者根据集成的不同,通过 LinkedIn 等其他渠道触达。这就是为什么我今天仍然认为这款应用有局限。我想先测试这部分归因,看看围绕这个问题是否有真正的关注度,然后再构建其他一切。我未来真正感兴趣的部分是收入挽回。通过将其与 AI 结合,目标将是适应不同的客户,了解哪些客户正在犹豫,并做更多不仅仅是展示数据的事情。我希望数据能够在产品内部真正发挥作用。我也很想知道你们今天是如何处理这个问题的。编码已经变得比以前容易得多,但一款好卖的好产品和一款无人问津的好产品之间的差异往往取决于营销和分发。我很希望听到你们对 Revliu 的反馈、我处理这个问题的方式,以及你们会采取哪些不同的做法。

译文由上游机器翻译生成,可能有误;判断请以英文原文为准。

英文原文(来源本站未改写)

I’m a founder and I just built RevliI’m a founder and I just built Revliu.After building several products, I always wanted to understand how my customers were actually finding me.Which campaign brought them in, which source they came from, and what their full journey looked like.There are already tools for this, but one problem I kept running into is that they often stop at first touch or last touch.That’s why I built Revliu around multi-touch attribution and the full customer journey.As soon as someone lands on your website, Revliu gives them an anonymous ID and starts tracking their journey.Once they sign up, that journey can be connected to the actual customer.

From there, you can see if they’re on a trial, how often they come back, how many sessions they open, and eventually when they pay.For me, this also makes it easier to talk to that user and understand why they decided to move forward at that specific moment.Today, Revliu tracks acquisition sources, returning visitors, sessions, touchpoints, and revenue.Instead of just knowing that a campaign got a certain number of impressions, I want to know how much money it actually brought in.Impressions are not really what I care about.The app itself is pretty simple.The main page gives you an overview of revenue by source.Traffic shows visitors, their journey, and their sessions.

Campaigns shows the acquisition funnel.For a SaaS, that can be visitor → lead → trial → paying customer.For an online store, it can simply be acquisition → purchase.Customers lets you look at each customer individually, see their touchpoints, where they came from, their journey, and when they bought.The technical side is simple in principle.It starts with an anonymous visitor who gets an ID.We keep track of their visits and touchpoints.When they sign up, that anonymous journey is connected to the customer.Stripe is connected as well, so when the customer pays, the revenue can be linked back to the same journey.

The goal is basically to connect acquisition → visits → signup → customer → revenue.Right now, the app is still in its first phase.I haven’t built all the integrations I want yet.What I want to build next is something that does more than just show data.If someone leaves their email but never finishes signing up, comes back several times without buying, or shows real interest without converting, I want to use that information to try to recover that potential customer.The idea would be to reach them again by email or, depending on the integrations, through other channels like LinkedIn.That’s why I still see the app as limited today.

I first want to test this attribution part and see if there’s real traction around the problem before building everything else.The part I’m really interested in for the future is revenue recovery.By combining it with AI, the goal would be to adapt to different customers, understand which ones are hesitating, and do more than just display data.I want the data to actually do something inside the product.And I’d really like to know how you’re handling this today.Coding has become much easier than it used to be, but the difference between a good product that sells and a good product nobody uses often comes down to marketing and distribution.

I’d really like your feedback on Revliu, the way I’m approaching the problem, and what you would do differently.

出处https://revliu.com/demo抓取日期 · 采集源 Hacker News

03 / EVIDENCE GAPS

这条还缺什么证据?

下面每条都由本条已有字段推出(等级、理由、商业模式、来源次数、是否演示), 本站不生成推测性结论;通用验证方法放在方法论页。

  • 可核验的收入或付费证据查官网定价页与付费口径;第三方数据源(如 GetLatka)只作旁证,需标注来源与时点。
  • 只有单一来源找一手站点或其他渠道是否重复出现同一产品;社区热帖数量不等于商业进展。

通用验证清单(谁有这个问题/谁愿意付费/一个人能交付哪一小步)见我们的筛选方法。

04 / SIGNAL HISTORY

发现时间线