Server-side tracking

When to use server-side tracking

Use the Events API when:

You need to record a conversion that happens entirely on the server (for example, a payment confirmation received via webhook)
You are building a server-rendered application without a browser front-end
You want to guarantee an event is recorded even if the visitor’s browser blocks JavaScript

Endpoint

POST https://ghostlyx.com/api/event

Headers

Header	Value
`Content-Type`	`application/json`
`User-Agent`	The visitor’s original User-Agent string

Request body

{
  "domain": "yourdomain.com",
  "name": "Purchase",
  "url": "https://yourdomain.com/checkout/success",
  "props": {
    "plan": "pro",
    "revenue": 49.99
  }
}

Field	Required	Description
`domain`	Yes	The domain as configured in GhostlyX
`name`	Yes	The event name. Use `pageview` to record a pageview.
`url`	Yes	The full URL where the event occurred
`props`	No	Object of string or number properties

Response

202 Accepted on success. No response body.

Example: cURL

curl -X POST https://ghostlyx.com/api/event \
  -H "Content-Type: application/json" \
  -H "User-Agent: Mozilla/5.0 ..." \
  -d '{
    "domain": "yourdomain.com",
    "name": "Purchase",
    "url": "https://yourdomain.com/checkout/success",
    "props": { "plan": "pro", "revenue": 49.99 }
  }'

Connecting to goals

Server-side events are matched to Custom event goals by event name, the same as client-side events.

Getting started

Analytics

Site health

Behaviour analytics

AI features

Sharing and teams

Developer reference

Data import guides

Account

Server-side tracking

When to use server-side tracking

Endpoint

Headers

Request body

Response

Example: cURL

Connecting to goals

​When to use server-side tracking

​Endpoint

​Headers

​Request body

​Response

​Example: cURL

​Connecting to goals

When to use server-side tracking

Endpoint

Headers

Request body

Response

Example: cURL

Connecting to goals