An original June 2026 scan of 507 church homepages: 72.0% carry a third-party tracker and 21.3% have the Facebook pixel (higher on giving pages). The method, the numbers, and what it means for a church's data.
In June 2026 we scanned the homepages of 507 U.S. churches to see what runs quietly in the background of a church website. Most carried a third-party tracker, and about one in five carried the Facebook (Meta) pixel — the same kind of tracker that, in documented cases, has sent sensitive visitor activity back to Facebook. Here is exactly what we did and what we found.
Churches hold a different kind of information than a store does. People visit a church website to read about grief, addiction, a crisis line, baptism, or where to give. Our case study on faith-app data looked at how faith apps, giving platforms, and data brokers handle that kind of data. This time we wanted a simpler question answered with real numbers: what is already running on churches' own websites — the front door most people actually use?
| Signal | Share of the 507 church homepages |
|---|---|
| At least one third-party tracker | 72.0% |
| Google Analytics | 59.8% |
| Google Tag Manager | 29.6% |
| Meta (Facebook) pixel | 21.3% |
| Session-recording (e.g. Hotjar) | 4.9% |
| Any advertising / identity tracker | 21.9% |
| Three or more trackers | 11.4% |
The short version: 72.0% of church homepages carried a tracker, and 21.3% carried the Facebook pixel — 108 of the 507 sites.
We then looked at church giving pages specifically. On the 71 churches where we could reach a donation page (common paths like /give or /giving), 26.8% carried the Facebook pixel — a higher share than on homepages. The advertising tracker most able to build a profile turns up most on the page where someone enters their name and a payment. That is rarely a decision anyone made on purpose; it is a website-builder default and an event-promotion habit landing on the one page where it fits least.
Most of this is ordinary, and worth saying plainly. Google Analytics sits on a large share of the entire web; a church staffer rarely chose it on purpose — a website builder bundled it. That is basic traffic counting, not an advertising pipe. Finding it on a majority of church sites is unremarkable.
The Facebook pixel is the part that deserves a second look. It is an advertising and identity tracker, not a traffic counter. As reporting we cite in the case study documented, a pixel placed on a sensitive page can report what a visitor did — including on a page about grief, addiction, giving, or a crisis line — back to Facebook, tied to that person's profile. Roughly one in five of the church homepages we scanned had one, and the rate was higher on giving pages. Almost none of those churches installed it to surveil anyone; they added it to promote an event and never thought about the person quietly reading the "I need prayer" page.
Session-recording tools, which we found on about 4.9% of sites, can replay what a visitor typed or clicked. On a contact or prayer form, that is a lot to hand a third party.
None of this means a church is selling anyone's data. It means that on a typical church website, a visitor's activity can flow to outside companies by default — usually without anyone on staff having decided that on purpose.
In our June 2026 scan of 507 reachable church homepages, 21.3% — about one in five — carried the Meta (Facebook) pixel, an advertising and identity tracker; the rate was higher (26.8%) on the giving pages we could reach. Because we only checked each homepage's initial HTML, the real figure across full sites is likely higher.
Not especially. Google Analytics is basic traffic counting and sits on a large share of the whole web; we found it on 59.8% of church homepages. The bigger privacy question is advertising and identity trackers like the Facebook pixel on sensitive pages, and session-recording tools that can replay what a visitor typed.
No. A tracker's presence is not proof that data is misused or sold. It does mean a visitor's activity can be shared with third parties by default — often without anyone on staff having chosen that. Our case study covers documented cases of where this has gone wrong.
Open your homepage, view the page source, and search it for connect.facebook.net or fbevents (the Facebook pixel) and hotjar (session recording). A free online tracker scanner will list them for you. Check your giving, prayer, and contact pages too — inner pages often carry more than the homepage.
No. AskMyChurch is anonymous by default — no accounts, no names, no device tracking — and it builds no profile of the person asking. Care needs surface as themes, never names or private words, and it does not sell or broker data.
Updated 2026-06-26 · AskMyChurch by Vision Genesis · Knoxville, TN
See it answer — try a live demo →