IPForge integration guide

Supported use cases

• Measure an organization's own links and persistent landing pages.
• Run transparent delivery or compatibility tests with owned or authorized inboxes, chats, recipients, and destinations.
• Review activity, source classification, and coarse device/session evidence inside the owning workspace.

A controlled test is diagnostic: a preview, image request, or browser event records what a delivery path did. It is not evidence that a named recipient read content, was at a precise place, or intended an action.

What the measurements mean

Human

A human classification means a capture contained browser signals and no currently recognized preview-bot, crawler, headless-browser, or hosting-network signal. It is a classification result, not proof of a person's identity, location, intent, or consent. Classifier coverage can change as services and signals change.

Unknown

unknown means the available signals were insufficient to make the classification. Unknown activity is excluded from human-oriented counts and must not be described as a human visit.

Deduplication

A repeat capture is marked duplicate when it has the same resource and fingerprint hash as an earlier capture within 24 hours. Human-oriented counters include only the first non-duplicate human capture in that window. This reduces repeat noise; it does not prove a unique person, since browsers, devices, networks, and fingerprints can change or be shared.

Device confidence

Device confidence is a coarse evidence read based on available browser/device signals, such as browser and OS family, device type, and whether signals agree or change over time. Use the phrase “same likely browser/device profile,” never “this is definitely the same person.” A fingerprint is technical evidence, not an identity credential.

Active dwell

Active dwell is opt-in, visible-tab time accumulated on a persistent IPForge landing page. Time pauses while the page is hidden; a short-lived session accepts small visible-time updates only. It does not measure reading, attention, or any activity after a redirect to a third-party destination. A redirect therefore means only that IPForge initiated the navigation, not that the destination loaded or was read.

Privacy and acceptable use

Use IPForge only in a workspace you own or are authorized to operate, for a stated purpose and with appropriate notice or consent. Owners should collect the minimum information needed for that purpose and honor applicable retention and deletion duties.

Do not use IPForge for covert person tracking, identity resolution, stalking, deceptive tracking links, or unauthorized surveillance. Do not collect credentials, keystrokes, form values, copied text, precise pointer paths, DOM/page contents, or other data outside the documented measurement scope. Do not give agents or public endpoints customer links, capture records, IP addresses, raw fingerprints, tokens, or implementation secrets.

API and MCP status

IPForge does not currently provide public API or MCP data access. The next integration phase is intentionally pending review of this guide and the measurement foundation.

If an owner-authorized API or MCP integration is released, it will use explicit workspace authorization, revocable scoped credentials, server-side ownership checks, and an audit trail. It will default to filtered, deduplicated summaries rather than raw visitor data; creating or publishing links and changing alerts or retention will require an explicit owner confirmation. Until then, no credential, endpoint, or tool should be inferred from this documentation.