Close

EveryPage connects to Close over OAuth and posts each read, download and form fill on your tracked documents to the matching lead in Close as a custom EveryPage activity. Reps see who read the proposal, how far they got and how long they spent, on the lead timeline they already work from, and can filter on it in Smart Views and Workflows.

Setup

1. Go to Account and find the Close card.
2. Click Connect Close and approve EveryPage in Close.
3. On connect, EveryPage creates one custom activity type called EveryPage in your organization, with the fields listed under What lands in Close. The sync starts with the default scope: all documents.
4. Adjust the sync settings that appear below the card, then click Save sync settings:
   • Which files: all documents, up to 20 hand-picked documents, or off.
   • Create leads for unknown readers: when a reader's email matches no contact in Close, create a lead (named after the email domain) with that contact and log the read as its first activity. Off by default.
5. Click Test connection to confirm the connection end to end. EveryPage calls Close with your token and checks that the EveryPage activity type and its fields exist, creating them if not. No activity is posted, because an activity needs a lead to attach to.
6. Optionally click Import recent reads to backfill history. See Backfilling history.

One EveryPage account connects to one Close organization. Reconnecting with a different organization replaces the connection.

How reads are matched to leads

A Close activity must belong to a lead, so EveryPage needs an email for the reader. The email comes from whichever of these applies:

• the per-recipient link the reader was sent (email invites and contact lists),
• the email gate on a public link,
• a form fill on the document.

EveryPage searches your Close contacts for that exact email. On a match, the activity is posted to the contact's lead, with the contact set so multi-stakeholder leads show who read. Matching is by exact email only; EveryPage never falls back to matching a company by email domain.

If there is no match and Create leads for unknown readers is off, the event is skipped. Anonymous reads with no email are always skipped, since there is nothing to attach them to. Skipped events are settled, not retried, and never count against the connection.

What lands in Close

Each event becomes one EveryPage activity on the lead with these fields:

The activity's timestamp is the event time, so it sits in the lead's timeline between the call before it and the email after.

Because these are standard custom activity fields, everything Close does with activities applies: Smart View filters such as "EveryPage activity with Read-through % over 80 in the last 7 days and no reply", Workflow triggers on a new EveryPage activity, and the Activity Overview report.

Events synced

The Close sync subscribes to a fixed set of three event kinds:

• Viewed: a reader opened the document. Posted as Event = Read.
• Downloaded: a reader downloaded the file. Posted as Event = Download.
• Gate completed: a reader submitted the email gate or a form on the document. Posted as Event = Form fill.

The connection and activity sync are available on every plan. The email gate itself is a Pro feature, so gate-completed events, and the lead-creation option that depends on them, only fire for accounts on Pro.

Backfilling history

Import recent reads posts past sessions as activities. You choose a window of 1 to 30 days and the import covers up to 250 sessions. The import is refused while a previous import or earlier deliveries are still pending, so wait for the queue to drain and try again.

Backfilled activities carry the time the session started, not the time you ran the import.

Pausing, errors and reconnecting

Close access tokens are short-lived and EveryPage refreshes them automatically. If Close revokes access, for example because the authorizing user was removed from the organization, the card shows Close access was revoked with a Reconnect Close button. After reconnecting, check the sync settings below the card.

If posting to Close fails repeatedly, EveryPage pauses the sync and the card explains why. The usual cause is the EveryPage activity type or one of its fields having been deleted in Close. EveryPage recreates a missing type or field on the next delivery, so click Resume syncing to continue. Deliveries that failed while paused are not replayed; use Import recent reads to fill the gap.

EveryPage respects Close's rate limits and spaces its requests per connection, so a document that goes viral will not starve your other Close integrations.

Disconnecting

Click Disconnect on the Close card. EveryPage revokes its tokens with Close and deletes the connection and its sync settings. Activities already posted stay on your leads; the EveryPage custom activity type is left in place in Close so existing Smart Views keep working. Delete it from Close's settings if you no longer want it.

Privacy

EveryPage posts only the fields listed above. Reader IP addresses are never stored or sent to Close, and EveryPage sets no cookies on your readers. Close grants every OAuth app full API access; EveryPage uses that access only to search contacts by email, create the activity type and post activities, and, when you turn the option on, to create leads.