docs

Two keys, and nothing to install

There is no code to add, no library and nothing to call. Everything below comes from the running app, so it cannot describe something that is not there.

Post links that carry the community

Every community you work gets a link on your own domain, never a short link on ours. A short link pasted into a community looks like a tracking link, and that is the thing that marks you as a spammer and costs you the trust you went there to build.

yoursite.com/?utm_source=reddit&utm_medium=community&utm_campaign=r-rails

Those are the standard parts of a web address that every analytics tool already reads. That is the whole setup. You paste the link into the community, and the numbers arrive on their own.

Connect two read-only keys

You set both at /setup. We store them encrypted and never write to either account. We never show a key back to you once it is saved.

  • Simple Analytics. Gives us the clicks each community sent you, read from the utm_campaign part of your links. Without it we cannot measure any community at all.
  • Stripe. A read-only key (it starts with rk_), never a full secret key. We match money to a product by its price id, so one Stripe account can serve several products without crediting the wrong one.

What we will not tell you

Your analytics knows a visit came from a community. Stripe knows someone paid. Nothing links those two records, and linking them by timing would be a guess.

So we count clicks for each community and money for each product, and we never claim to know which community won you a particular customer. We can still answer about a community that costs you real time and sends almost nobody, because that answer uses numbers we actually have.

We never receive a name or an email address, and no screen ever shows one of your customers.

Questions →