GratisAI business · bound unique reach when channel totals cannot reveal their overlap · local-first FREE TIER 1 Free Run Available
overlap-bounds range sheet · plotted bar chart sheet

Bound Unique Reach When Channel Totals Cannot Reveal Their Overlap

Two channels can each reach hundreds of people without reaching hundreds of different people. Show the bounds implied by marginal totals before reporting a combined audience or frequency.

1 · Channel code | unique reached users within channel | impressions within channel

FIRST-LOAD

HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.

Data note: This overlap-bounds range sheet calculates in the tab from Channel code | unique reached users within channel | impressions within channel. No input-collection endpoint, AI request or file upload is built into it. Drafts may be saved locally; explicit input-state links and optional external formatting can disclose the records. Use non-sensitive codes and clear the draft when finished.

Perspective: Before: summed channel totals masqueraded as deduplicated people. After: marginal counts expose a bounded union and a conditional frequency range without invented overlap.

2 · Read the overlap-bounds range sheet

Aggregate-count bounds only: no identity deduplication, attribution, conversion inference or performance guarantee. Verify a common audience/window and metric definitions with the responsible analyst; use only approved non-sensitive aggregate evidence.

Optional filing controls are a local prototype.

Checkout is unavailable. The reading above is complete; print, CSV and five local summaries are optional enhancements, not hidden answers.

Before using the overlap-bounds range sheet

Use aggregate, non-sensitive channel totals for the same time window and the same defined audience universe. Each channel’s reach must already be deduplicated within that channel. The app does not join identities, fetch analytics or estimate overlaps from impressions. A supplied common universe caps the possible union, but it must actually contain every counted person; different populations or windows invalidate the model. The range describes what remains unknown with marginal counts alone. It is not uncertainty from a sampled confidence interval and does not assign likelihood to any possible overlap arrangement. No conversion, attribution or return-on-spend conclusion is available.

Boundary and sources

Aggregate-count bounds only: no identity deduplication, attribution, conversion inference or performance guarantee. Verify a common audience/window and metric definitions with the responsible analyst; use only approved non-sensitive aggregate evidence.

Mechanism: competence-autonomy-loop

Optional AI formatting, never the calculation

Manual entry completes this overlap-bounds range sheet for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.

Format only these fictional or non-sensitive notes for a overlap-bounds range sheet. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string"]}], "setting": "string"}. The columns are Channel code | unique reached users within channel | impressions within channel; the setting is Common audience-universe size (users). Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.

An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.