We built the version that asks first.

Why this exists

Roughly 3% of website visitors fill out a form, and about three quarters of organizations never identify the rest. For a business that is a marketing inefficiency. For a campaign it is the largest pool of warm, self-selected, locally-relevant supporters it will ever have access to, evaporating daily.

There were already tools that solved this by not asking. We think that approach is both wrong and, increasingly, legally precarious — the California wiretapping and pen-register cases are aimed at exactly the behavior of firing before the visitor is asked. So we built the version where the identification logic cannot execute until consent is granted, and where the evidence of that consent travels with every record forever.

What we will not build

There is no configuration that disables the consent gate. Not for a large customer, not for a state where you believe you are exempt, not for the last two weeks of a cycle. There is no setting that sends an ad-platform conversion event for a visitor who declined ad consent. And there is no path where we sell, rent or pool supporter data.

The honest cost of all of that: we identify fewer visitors than a vendor who does not ask. We would rather say it here than in a bake-off.

Nonpartisan, and specific about what that means

One rate card, applied the same way to every similarly-situated campaign, regardless of party — which under FEC rules is closer to a requirement than a preference. Our integration directory covers 53 platforms across both lanes, filterable so you see what applies to you, and the coverage is deliberately even: NGP VAN and i360, ActBlue and WinRed, Scale to Win and RumbleUp.

Two things we are uncertain about, on purpose

We do not publish a single confident date for the recent California pen-register rulings, because the dockets are genuinely easy to conflate and we would rather describe the holding than correct a date later. And we tell you to verify current 10DLC political registration requirements against Campaign Verify and your carrier's own documentation, because a lot of circulating dates come from vendor blogs rather than primary sources.

A vendor who is certain about everything in this area has not read enough of it.

What we do not have yet

• Voter file matching. No party registration, vote history or district. That requires a data partnership we have not signed — see voter file rules.
• SOC 2. Not certified today, and we are not displaying a badge for an audit in progress. The controls we do have are on security & privacy.
• Several native connectors. Gated behind marketplace reviews and partnerships we do not control. Every one is labeled.