Skip to content
Meta and ChatGPT Ads

Delete Meta destination

Removes the property's Meta Conversions API destination and its stored credential: purchases stop going to Meta.

DELETE /companies/{companyId}/properties/{propertyId}/destinations/meta

Scope setup · Access Deletes; cannot be undone (productmetrics needs --yes) · Operation id destinations.delete_meta

Try it

productmetrics runs after productmetrics login; curl needs PM_TOKEN (see Authentication). Set $COMPANY_ID, $PROPERTY_ID first.

productmetrics destinations delete-meta \
  --company-id $COMPANY_ID \
  --property-id $PROPERTY_ID \
  --yes \
  --json

Response

API response (200):

{
  "data": null,
  "request_id": "req_01JRPY0PJK536DT7T2NR97EN1X"
}

The route answers with no content, so data is null: the destination and its stored access token are gone.

CLI output: productmetrics destinations delete-meta --json prints { "ok": true, "data": …, "request_id": "…" } with the same data.

Before you call

Cannot be undone; setting it up again needs the credential from the person, so confirm with them first. Needs editor or admin access.

Path parameters

NameTypeDescription
companyIdstring (uuid)Your workspace id, from productmetrics whoami or properties.list (company_id).
propertyIdstring (uuid)The property id, from productmetrics whoami or properties.list (property_id).

Errors

A failure answers with its HTTP status and { error: { code, message, details? }, request_id }. Branch on code (stable, lower_snake); show message to the person. The CLI prints the same error with "ok": false.

{
  "error": {
    "code": "insufficient_scope",
    "message": "This operation needs the setup scope; connect again and allow it.",
    "details": {
      "required_scope": "setup"
    }
  },
  "request_id": "req_01J21HCY53ZZEKKQRRHAKQSJSR"
}
StatusCodeWhen
400invalid_requestA path, query or body value does not match this page. details.issues lists each location, path and message.
401invalid_tokenThe token is missing, expired or revoked: sign in again (productmetrics login). The WWW-Authenticate header says why.
403insufficient_scopeThe token lacks the setup scope (details.required_scope): sign in again and allow it.
404not_foundAn id in the path does not exist, or the signed-in person cannot open it.
429rate_limitedMore than 600 requests a minute for this person: wait the Retry-After seconds (60) and retry.

All Meta and ChatGPT Ads operations