AdnovaDocs
Ad Launcher

Update tracking spec

Overwrites the ad account's stored trackingSpecs. The launch worker reads this value at launch time so subsequent ads use the configured pixel and app id automatically — you do not need to repeat them on every launch request. Look up the available pixel ids via List pixels and apps via List apps.

PUT
/meta/ad-accounts/{adAccountId}/tracking-spec

Authentication

authentication
api-key<token>

Create an API key from the Adnova dashboard (Account integrations). Pass the key value in the api-key request header on every call.

In: header

Path Parameters

adAccountId*string
Length1 <= length

Header Parameters

x-workspace-id*string

Workspace the request operates in. Get it from List workspaces.

Length1 <= length
x-org-id*string

Organization context (required on every endpoint). For lookup endpoints the org is derived from the ad account in the URL, so any org id you have access to is accepted.

Length1 <= length

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X PUT "https://api.adnova.ai/ad-launcher/v1/meta/ad-accounts/string/tracking-spec" \  -H "x-workspace-id: string" \  -H "x-org-id: string" \  -H "Content-Type: application/json" \  -d '{    "website_pixel_id": "987654321098765"  }'
{
  "website_pixel_id": "987654321098765",
  "app_id": "1234567890123456",
  "androidAppDeepLink": "string",
  "iosAppDeepLink": "string"
}
{
  "error": {
    "code": "string",
    "message": "string"
  },
  "message": "string"
}
{
  "error": {
    "code": "string",
    "message": "string"
  },
  "message": "string"
}
{
  "error": {
    "code": "string",
    "message": "string"
  },
  "message": "string"
}
{
  "error": {
    "code": "string",
    "message": "string"
  },
  "message": "string"
}
{
  "error": {
    "code": "string",
    "message": "string"
  },
  "message": "string"
}
{
  "error": {
    "code": "string",
    "message": "string"
  },
  "message": "string"
}