Network numbers
The venue's own ledger, in public. Updated hourly; last computed 2026-09-19 02:00:57 UTC.
0
counted ad views · last 30 days
0
counted clicks · last 30 days
74
real trades cleared (all time)
11
live listings · 2 sellers
670
counted ad views (all time)
64
under-delivered trades auto-refunded
Honest context: every counted figure above comes from our own impression counter and nothing else. Preview flights that settled without counter telemetry are excluded entirely rather than labelled - if our counter did not see it, it is not on this page, so a small number here is a true number, not a modest one. The venue is in invite-only preview and no revenue figures appear while payments run in test mode. Delivered counts are ad views (an ad unit rendering), never "people reached."
The network behind this venue
This venue's own counting engine went live Jul 25 and counts only what it serves. The network behind it has been delivering since 2009.
These are not counted by this venue's own counter above - each figure below is counted by the platform named on its tile. Two separate ledgers, never added together.
4,051,233
ad views · last 30 days (EPOM built-in range)
EPOM-counted
4,213
clicks · last 30 days (EPOM built-in range)
EPOM-counted
6,650,000
impressions · trailing 90 days
DV360-reported
Lifetime ad views since 2009 - audit in progress, not printed until it's provable from records
EPOM figure as of Jul 25, 2026 (built-in 30-day range - EPOM's custom date-range API is currently broken, so this is not a hand-picked window). DV360 figure sourced Jul 21, 2026, scheduled re-pull Aug 3-4 2026. Both are the wider MuslimReach network's own platform-reported delivery, run by MAN since 2009 - not a measurement this venue's counter produced, and not blended with the counted tiles above.
How we count
The rules the counter runs on - so you never have to take a number on trust.
- Counted on ad-unit render. One served ad = one ad view, counted when the unit renders - not on MRC-viewable time. These are self-reported counts from our own counter: not third-party audited, not MRC-accredited, and not a viewability measure. We say so wherever the number appears.
- Counted means counted. A number appears on a public surface only when our own counter produced it. Delivery settled without counter telemetry (a preview or concierge flight) is recorded separately and never added to a published total - the buyer still sees it on their own receipt, marked as a stand-in.
- Bot-filtered and de-duplicated. Known bot, crawler and headless user-agents are rejected before counting; duplicate loads are collapsed by a short-window dedupe. The dedupe errs toward under-counting: two people behind one network address in the same minute count once. IP and user-agent are used only for de-duplication and bot filtering - never stored as a profile, never targeted on.
- Roughly three quarters of raw ad requests are bots, and never get counted. In our own server logs since 25 July 2026 - a few days on a handful of our own pages, so a small sample - about 74% of raw requests to our ad units came from known bots and crawlers and were rejected before counting. Our own automated site-testing browser is filtered out too: our robot is not an audience. We publish the ratio rather than the flattering number, and we expect it to move as more supply comes on.
- Contextual targeting only. Ads match what a page is about. No cross-site tracking, no demographic inference, no individual profiles.
- Declared vs measured, always labelled. A publisher's own estimate carries the gold ◆ "declared" mark; a measured figure comes from this counter. The two are never blended.
- Discrepancy detection. Stored delivery is reconciled against the live counter; mismatches are flagged, not smoothed over.
- Under-delivery auto-refunds. A campaign that delivers less than it cleared for refunds the difference to the buyer's wallet automatically.
- Our take is a disclosed 20%. Publishers keep 80% of every cleared trade. The rate is the publisher's or the market's - never ours to fix.