Tracking reference: pixels, click links, and page beacons
What InfluencersKit tracks automatically, the endpoints and cookies involved, and why there's no snippet to install on your site.
There's nothing to install. InfluencersKit adds tracking to the emails, landing pages, and forms it serves. This page lists what runs, for anyone reviewing it for privacy or debugging.
In email
Each event stores the campaign, recipient, time, user agent, and IP address (the visitor's own address, not one they can set in a header). How these turn into report numbers is in how counting works.
| Request | What it does |
|---|---|
GET /t/open/{messageId}.gif?r=… | A 1×1 image, sent with no-store caching. Records an open. |
GET /t/c/{token} | Records a click, then redirects with a 302 to your link. |
GET /t/click/{messageId} | An older click link format (emails sent before June 2026). It redirects only to a link that was in that email, or to an InfluencersKit page; any other address gets a page that shows it and asks before going on, and no click is recorded. |
On landing pages and forms
Each page load sends a beacon to POST /api/public/analytics/track. The server looks up the country from the IP address to decide whether consent is needed. What it stores depends on consent (below); it never stores the IP itself, and the hash it keeps after consent is keyed with a server secret.
{
"resourceType": "form",
"resourceId": "…",
"sessionId": null,
"visitorId": null,
"referrer": "https://example.com/blog",
"pageUrl": "https://example.com/newsletter",
"consentGiven": false
}Response:
resourceTypeisformorlanding_page.sessionIdandvisitorIdare left out of the response when consent is required.- An unknown resource returns
{ "requiresConsent": false }and records nothing.
{ "requiresConsent": false, "sessionId": "…", "visitorId": "…" }Cookies
| Cookie | Lifetime | Purpose |
|---|---|---|
ik_vid | 365 days | Visitor ID, used for unique and new visitors |
ik_sid | 30 minutes | Session ID |
ik_consent | 365 days | The visitor's choice: 1 accepted, 0 declined |
Consent
- Visitors from the EU, EEA, and UK, and visitors whose country can't be determined, see a banner with Accept and Decline.
- Until they accept, only a count is stored: the form or page and the hour. No IP hash, location, browser, referrer or page address, and no
ik_vidorik_sidis issued. Declining keeps it that way. - If they accept, a second beacon sets those cookies and the full record starts: page, referrer, browser and operating system, approximate location, and a keyed hash of the IP.
- Visitors from elsewhere get the full record with no banner.
The Behavior Tracking page
The Behavior Tracking page merges email opens and clicks, shown as email_open and email_click, with any custom events on your account. Its ranges are 7, 30, or 90 days, and its subscriber list shows up to 100 people.
Engagement score there is opens × 0.5 + clicks × 1.5 + a small amount for total events, capped at 10. For what the page is for, read behavior tracking.
Its Automation Rules act on these same opens and clicks, so machine opens and link scanners can fire them. See behavior tracking before you build one.
Frequently asked questions
Is there a JavaScript snippet to track subscribers on my website?
No. Behavior Tracking covers email opens and clicks. To track visits to a form on your site, embed it with the Script snippet.
Can I send my own events from my site or app?
Not with a public endpoint. Recording a custom event needs a signed-in dashboard session, so it doesn't suit a website or a server job.
Ready to try it?
Open your dashboard and follow along — or create a free account.