What can a church know about who it reached, without tracking anyone?
More than a headcount and less than a profile. A church can know how many people listened, in which languages, how long they stayed and what they read afterwards, all counted without a name, a login or a cookie. Who those people are is a different question, and the only honest answer is: the ones who chose to tell you.
Why a headcount is not enough, and a profile is too much
A church that translates its services is making a decision about people it cannot see: which languages to keep paying for, whether the Farsi group is growing, whether anyone actually listens to the Armenian voice, whether the visitors on Easter Sunday came back. A headcount at the door answers none of that. Guessing answers it wrongly.
The tools that answer it best are the ones the web already has, and they answer it by identifying people: an account, a cookie, a device. For a church that is the wrong trade. Attendance at a service is data about religious belief, the most protected category in the GDPR, and a congregation that discovers it was being tracked to help the media team make a chart will not forgive the media team.
What can be counted without a name
- How many listened, per service and per language, and how that changed week to week.
- How long they stayed: whether the German voice lost half its listeners at minute twenty.
- What was read afterwards: which language's transcript, which piece of content, how many downloads.
- How many pressed “Amen”, as a number and nothing else.
- How many said it was their first time — because they said so, not because a device was new.
Every one of these is a count. None of them needs to know who a listener is, and a tool that says it needs identity to produce them is choosing to have it.
The line that must not be crossed
Engagement and pastoral care are different things and should stay in different places. Engagement is anonymous numbers for a decision. Pastoral care is a person who wants to be known: a visitor who ticks “this is my first time”, leaves a language and a way to reach them, and agrees to be contacted. The second should never be inferred from the first. A church that works out who a listener is by matching their device across Sundays has crossed the line, whatever it then does with the knowledge.
A simple test: could the church, from its engagement numbers alone, say that the person who listened last Sunday is the person who listened this Sunday? If yes, it is tracking. If no, it is counting.
What to ask a tool that offers church analytics
How Sanctavo does it
Nobody signs in to listen and no cookie identifies a listener. Sanctavo counts: how many listened per language, how long, what was opened and downloaded afterwards, and how many pressed Amen, which stores no identity at all. A listener becomes known to the church only by choosing to — first time here, a prayer request, a way to be reached, each a switch the church turns on per service and each recorded with consent. What they leave is private to the church, never shown publicly, and deleted with the service. The two never meet: engagement numbers are anonymous and stay separate from pastoral care.