Tracking - Public

Track visitor event

Track visitor event from frontend. Uses background task for fire-and-forget performance.

Plain def: the website lookup is synchronous (a per-worker cache in front of pyodbc), so it runs in the threadpool, never on the event loop. Unlike /tracking/events/batch below — one Redis push, deliberately async.

post/public/tracking/event

Request

  • Base URL
    https://api.multigest.pt (the document declares no server; this is the origin it was published from)
  • URL
    https://api.multigest.pt/public/tracking/event
  • Auth
    API key in header x-api-token and API key in header x-origin-verify

Headers

x-website-tokenstring nullable

Request body

visitor_idstring required

Unique visitor identifier (UUID)

event_typestring required

Event type: page_view, form_submit, click, scroll, engagement

page_urlstring required

Current page URL

page_titlestring nullable

Page title

event_namestring nullable

Specific event name

metadataobject nullable

Additional event data

Response

Successful Response

unknown required

Changes

No recorded changes to this operation across all 21 revisions of this API.