Server-side hits

When to use it

When you cannot put the tag on a page, or you want your server to decide what counts as a visit. Your server reports the visit and gets the signed hit back to keep.

The call

POST https://go.hitctrl.com/hits
x-api-key: your API key

{
  "link": "lp_7Kq2",
  "source": "jane-doe",
  "subIds": { "s1": "summer", "s2": "banner-a" },
  "ip": "203.0.113.7",
  "userAgent": "Mozilla/5.0 …",
  "referrer": "https://news.example/"
}

• link: the landing page ID (the link's linkId); source: the Partner ID (the link's sourceId); subIds: the sub IDs s1–s5 (the link's affS1–affS5).
• ip and userAgent: the visitor's, so bots and limits are checked as for the tag.
• Optional country, region and city when your server already knows them; otherwise they come from the IP address.

link, ip and userAgent are required. Leave out source for your team's own links: they count for the workspace, with no partner.

The answer holds the signed hit (and expiresAt, when it stops counting) to send with the conversion later. Missing fields answer missing_params; a wrong IP address invalid_ip_address.

Good to know

• The same checks apply as for the tag: partner, landing page, offer, access, bots and limits.
• Use an API key from Settings › Developers. When the key has an IP allow-list, only those addresses may call.