Record a UTM-tagged landing arrival

Called by the marketing site's own beacon to attribute an outbound-email click to the lead it was sent to. Not useful to call directly: a request with no UTM parameters is accepted but produces no row, and no cookie, IP, or user agent is ever stored.

post/api/landing/visit

Request

  • Base URL: https://app.atisbo.dev
  • URL: https://app.atisbo.dev/api/landing/visit
  • Auth: none declared

Headers

X-API-Versionstring
Example:1.0.0

Optional. States which contract version your client was written against. Absent or equal to the current version (1.0.0) changes nothing. A well-formed but different version is accepted: the response keeps reporting the version THAT ANSWERED in x-senso-api-version, and if the requested version is declared deprecated the response additionally carries RFC 8594 Deprecation and Sunset dates. A value that is not three dot-separated integers is rejected with 400 and code invalid_api_version BEFORE the operation runs. Negotiated on this operation only; other /api/* paths ignore the header.

Response

Accepted (a row is written only if at least one UTM value was present).

okboolean required
recordedboolean

Changes

No recorded changes to this operation across all 1 revision of this API.