Basic plan

Email invites

Send tracked email invites to named recipients with per-recipient links that attribute opens and satisfy the email gate.

Email invites let you send a document to specific people while tracking exactly who opened it. Each recipient receives their own tracked link with a unique token, so views are attributed to them by name in your readership analytics.

How invites work

When you send an invite, the system creates a unique, unguessable link for each recipient. That link carries a per-recipient token (?i=<token>) which serves three purposes: it attributes the view session to that person, it satisfies the email gate server-side so nothing the recipient types is validated or captured, and it supplies their identity for watermarking — the invitee's email is stamped onto watermarked pages, taking precedence over any email captured by the gate.

Each recipient gets their own invite record with a token generated from 192 bits of cryptographic randomness. The tracked link is built from your file's durable short identifier (never the custom-domain slug, which can be renamed or removed) plus the recipient's token and an email attribution source parameter.

Emails are dispatched asynchronously from the request, so invite rows are created synchronously first (and count toward your daily cap immediately). The system throttles outbound sends to respect email rate limits.

Tiers and limits

Invite sending requires the basic plan or higher. Free-tier users cannot send invites at all.

Basic plan

You can send up to 10 direct email addresses per send request. Distribution lists require Pro, so on basic you enter addresses directly. Your plan has a daily cap of 50 invites across all your files. The daily cap is per-user and resets at UTC midnight.

If you send multiple emails in a single request and any of them fail validation (malformed address, or a duplicate of another address in the same send), those addresses are silently skipped and do not count toward the per-request limit or the daily cap.

Pro plan

You can send invites directly, with no per-request limit, or use a distribution list — a saved contact list that you manage separately. When sending via a list, you send to everyone in that list at once. Either way, only the daily cap applies.

Your plan has a daily cap of 1000 invites across all your files. The daily cap is per-user and resets at UTC midnight.

Exceeding the cap

If a send request would push you over your daily cap, the entire request is rejected with an HTTP 429 (Too Many Requests) response. The response body includes your daily ceiling and how many invites you have already sent today, so you can plan your next send. Try again after midnight UTC, or consider upgrading your plan for a higher daily allowance.

The invite.viewed webhook

The first time an invitee opens their tracked link, EveryPage emits an invite.viewed webhook event to your subscribed endpoints. The payload carries the document's fileUuid and fileName plus the invitee's email and name.

It fires once per invite — the first open only, not on subsequent visits — and never for a view by the document's own owner. Because the token satisfies the gate server-side, no gate response is recorded, so an invited open emits invite.viewed rather than gate.completed.

Note a current rough edge: on a document with an email gate, the viewer still renders the gate form to an invited recipient even though their token has already satisfied it server-side. Whatever they type is neither validated nor captured, and the token — not the typed address — remains the identity used for attribution and watermarking.

Invites vs. share-by-email

Email invites and share-by-email are two different ways to distribute your document:

  • Email invites create a tracked link unique to each recipient. The recipient's identity is carried in the URL token, views are attributed by name, and the token satisfies the email gate on their behalf.
  • Share-by-email sends the ordinary share link to one recipient at a time, with an optional note. The recipient is not identified; they receive the same link anyone with the URL can access. If your document has an email gate or a password, they must still pass it to open the document.

Use email invites when you want to know exactly who opened your document and attribute views to individuals. Use share-by-email to quietly notify someone of a shared document without per-recipient tracking.