Update a tracking tag
Partial-update a pixel. Whitelisted fields: name (rename),
enableAutomaticMatching, automaticMatchingFields,
firstPartyCookieStatus, dataUseSetting. At least one is required.
Returns the re-fetched canonical tag. Meta only (platform metaads);
other platforms return 405.
There is no DELETE — Meta has no API to delete a pixel. To stop using
one, unshare it from your ad accounts (DELETE .../tracking-tags/{tagId}/shared-accounts) or disable it in Events
Manager.
Authorization
bearerAuth API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
Pixel id.
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
At least one field is required; the route returns 400 if the body is empty.
Response Body
application/json
application/json
{ "platform": "metaads", "tag": { "id": "string", "name": "string", "platform": "metaads", "kind": "pixel", "status": "active", "code": "string", "lastFiredTime": 0, "isUnavailable": true, "installed": true, "creationTime": 0, "ownerBusinessId": "string", "ownerAdAccountId": "string" }}Set ad tracking tags
Unified update. Send only the fields for the ad's platform: - Meta: `urlTags` (array of {key,value}). Meta creatives are immutable, so this rebuilds the creative and repoints the ad. By DEFAULT we PRESERVE the existing creative verbatim (re-post its object_story_spec + the new url_tags, reusing the image), so you send `urlTags` ALONE — no need to read back headline/body/CTA. `creative` (headline, body, callToAction, linkUrl, imageUrl) is OPTIONAL and only needed to rebuild explicitly, or for SHARE / page-post / dark / asset_feed creatives whose object_story_spec Meta strips (those return 422 asking for `creative`). - Google: `trackingUrlTemplate` and/or `finalUrlSuffix` (full template strings; account quota applies). - LinkedIn: `dynamicValueParameters` and/or `customValueParameters` (campaign-level Dynamic UTM).
Share with an ad account
Shares the pixel with another ad account so campaigns/audiences in that account can use it. Requires that you administer both the pixel's owning Business Manager and the target ad account; a pixel on a personal (non-BM) ad account can't be shared (Meta will reject the call). Meta only (platform `metaads`); other platforms return 405.