Should You Ask for an Email Before Someone Can Open Your Document?

An email gate is a door in front of your document. Someone follows your link, sees a single field asking for an address, types one, and the document opens. Nothing is sent to them, nothing is confirmed, and nothing stops them typing whatever they like.

Doors cost readers. The only question worth asking is what you get for the ones you lose, and the answer is more specific — and smaller — than the way gates are usually sold.

What a gate buys you

1. An address at the moment of intent. Somebody wanted your document enough to hand over an address in exchange for it. That is a genuinely different signal from an address collected in any other way, because it was given at the exact moment the person wanted something from you.

2. A name on a read you could otherwise never attribute. If you mailed the link to a named person, you already know roughly who your reader might be. If the link is on a website, in a listing, or three forwards deep inside a company you have never spoken to, there is no address anywhere in the picture. The gate is the only route to one.

3. One person instead of two. A reader who passes the gate on their phone and again on a laptop is counted as one person rather than two browsers, because the address they typed is the same. Without a gate those are two anonymous readers and your count is quietly overstating your audience.

What it does not buy you

Verification. Nobody checks the address, no confirmation is sent, and the document opens the instant it is typed. Quixli labels it self-reported everywhere it appears — on the session, in the reader list, and in the alert email — rather than presenting it beside a confirmed one as though the two were the same kind of fact.

The practical reading: a gate address means “somebody who wanted this said they were X”, not “X read it”. That is still worth a great deal. It is not identity, and a tool that shows it to you as identity has made your data worse while appearing to make it better.

It is also not, by itself, a relationship. What a gate collects is an address someone typed to get past a door, and treating a door as a subscription is how a useful signal becomes a complaint.

The cost is real and invisible in your own numbers

This is the part that catches people, and it is a measurement problem rather than a marketing one.

The readers a gate turns away do not appear anywhere. They are not a bounce you can look at, not a failed session, not a row in a list. A gated link with forty reads and an ungated link with forty reads look identical, and the gated one may have turned away several times that number on the way in. You cannot see the loss by looking harder at the screen, because the loss is defined by its absence from it.

Which means the only honest way to know what a gate costs you is to measure it across sends rather than within one:

• Pick one kind of document and one kind of recipient. Mixing a cold listing with warm proposals answers a question you did not ask.

• Gate half the sends and leave half open, and keep everything else — subject line, channel, timing — the same.

• Compare reads per send, not anything measured at the gate itself. A gate’s own completion rate only counts people who reached it, which is the population you are trying to measure the size of.

• Run it until it is boring. A handful of sends will tell you a story and it will be the wrong one.

We have not published a figure for what a gate costs in readers, and you should be sceptical of anyone who quotes you one for your audience. It depends entirely on who is on the other end and how badly they want the document — which is exactly what the test above measures and a benchmark cannot.

When a gate earns its place

• A link you cannot address. Posted on a site, sent to a list, included in a directory, or circulating somewhere you have no visibility into. Here the gate is the difference between knowing something and knowing nothing.

• A document worth the door. A substantial report, a piece of research, a template somebody actively went looking for. The exchange has to feel proportionate to the person making it.

• A document you expect to be forwarded. A gate is the only mechanism that puts a name on a reader you never mailed — the forwarding problem in full.

When it is just a tax

• A named client who is expecting it. You already have their address. The gate buys you a copy of something you have and charges a client, mid-decision, for the privilege of reading the thing they asked you for.

• A proposal after a call. You know exactly who is opening it. Send it to their address, and let the send itself be the attribution.

• Anything time-critical. A door in front of an urgent document is a door in front of an urgent document. The address is not worth the delay and the irritation is not free.

Where it applies

A gate belongs on a public link — the kind anyone with the URL can open — because that is the only kind of share with an unknown reader on the other end. Shares sent to an address, a domain or your own team are already addressed, so a gate there asks a question that has been answered. In Quixli it is a paid-plan control, switched on per link rather than per account, so a gate on one document does not put a door in front of everything else you have sent.

New to reading this kind of signal at all? Start with how do you know if someone read your proposal. What the paid plans include, and what Free shows without one, is on the pricing page.