Skip to content
Stores and tracking

Get enhanced conversions readiness

Whether Google Ads enhanced conversions are ready for the property, from the last stored check: the readiness state, whether the account (or its manager account) accepted Google's customer data terms, and Data Manager's answer.

GET /companies/{companyId}/properties/{propertyId}/tracking/enhanced-conversions

Scope read · Access Read only · Operation id tracking.get_enhanced_conversions

Try it

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

productmetrics tracking get-enhanced-conversions \
  --company-id $COMPANY_ID \
  --property-id $PROPERTY_ID \
  --json

Response

API response (200):

{
  "data": {
    "companyId": "2a7d9b3c-1e4f-4a5b-8c6d-7e8f9a0b1c2d",
    "propertyId": "8c1f4d2e-7a3b-4c5d-9e6f-0a1b2c3d4e5f",
    "state": "not_connected",
    "googleAdsCustomerId": "1234567890",
    "conversionCustomerId": "1234567890",
    "customerDataTermsAccepted": true,
    "enhancedConversionsForLeadsEnabled": true,
    "dataManagerAccepted": true,
    "dataManagerReason": "Example message.",
    "checkedAt": "2026-11-02T09:30:00.000Z",
    "errorCode": "credential_unavailable",
    "settingsUrl": "https://example-store.com",
    "enhancedConversionsUrl": "https://example-store.com"
  },
  "request_id": "req_01JAV722QJ1RJG8GQCNKMJ63NE"
}

CLI output: productmetrics tracking get-enhanced-conversions --json prints { "ok": true, "data": …, "request_id": "…" } with the same data.

Before you call

Accepting the customer data terms is something the person does themselves in Google Ads.

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 read scope; connect again and allow it.",
    "details": {
      "required_scope": "read"
    }
  },
  "request_id": "req_01JGDMAZ5EZB6CBE7SN5762390"
}
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 read 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 Stores and tracking operations