Skip to main content
Use overlap when you want to combine topic research signals with activity on your own website. Use audience analytics when you want to understand how a saved audience changes between completed runs.

​
Choose the scope

These operations support organization API keys. Use an audience owned by that organization.

​
Retrieve website overlap

The organization-wide endpoint compares the latest completed audience runs with recent identified website visitors. It deduplicates people by email hash and includes their latest audience matches. This is an overlap result, not a list of every website visitor or every Orbit contact. Read the response state before interpreting an empty result. no_completed_runs means there are no completed snapshots to compare. Inspect lookbackDays, total, limit, and offset in the generated reference when building reporting and pagination. For one visitor’s topic history, use the 64-character SHA-256 identifier required by the path and optionally scope with audienceId. Topic history describes matches in audience runs; it does not expose a person’s full browsing history.

​
Compare completed runs

The audience dashboard compares the latest completed run with the previous completed run. Trends provide chronological metrics across completed runs. Keep run dates in reports so readers know which snapshots were compared. A preview, a current audience definition, and a completed run can describe different populations. Updating an audience config affects future runs rather than rewriting older results. Use the generated references under Visitor overlap and analytics for exact parameters and response fields. See Audience runs to produce a new snapshot.