POST /api/v1/campaigns/click — Track User Clicks

Call this endpoint when a user clicks or otherwise interacts with a displayed campaign. A click event signals genuine user engagement to the ENS Ads platform and is used by advertisers to measure campaign performance. You should fire this request in response to a real user action — for example, after intercepting the click on a campaign element before navigating the user to the destinationUrl.

This endpoint must be called from your server. Your API key must never appear in client-side or user-facing code. Forward click events through your backend to keep your credentials secure.

Endpoint

POST https://ads.enslive.live/api/v1/campaigns/click

Content-Type: application/json

Request example

curl -X POST "https://ads.enslive.live/api/v1/campaigns/click" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "campaignId": 1,
    "placement": "header_banner",
    "location": "US",
    "device": "mobile"
  }'

Body parameters

integer

required

The unique ID of the campaign that was clicked. Use the id field returned by the Fetch Campaigns endpoint.

string

required

The placement ID where the campaign was rendered when the user clicked (e.g., header_banner, article_inline). This must match the placement used when fetching and displaying the campaign.

string

The ISO 3166-1 alpha-2 country code of the user’s geographic location (e.g., US, GB, FR). Including this improves reporting accuracy for advertisers.

string

The device type of the user who clicked the campaign. Accepted values: mobile, desktop, tablet.

Response

200 — Success

{
  "status": "success",
  "message": "Click tracked successfully"
}

400 — Bad Request

Returned when a required field is missing from the request body.

{
  "status": "error",
  "message": "campaignId is required"
}

401 — Unauthorized

Returned when the Authorization header is missing or the API key is invalid.

{
  "status": "error",
  "message": "unauthorized"
}

Only track clicks that result from genuine user-initiated interactions. Do not fire this endpoint programmatically, on page load, or in response to automated events. Tracking fraudulent clicks violates advertiser trust and platform terms, and may result in your API key being suspended.

​Endpoint

​Request example

​Body parameters

​Response

​200 — Success

​400 — Bad Request

​401 — Unauthorized

Endpoint

Request example

Body parameters

Response

200 — Success

400 — Bad Request

401 — Unauthorized