Adobe Target AB Activity REST API does not round-trip additional metric configuration used by the UI

I’m seeing a mismatch between the public Adobe Target Admin API for AB activities and the Adobe Target UI.

The issue is that additional metric configuration shown in Goals & Settings is not fully available in the public REST activity model.

Observed behavior

For additional metrics in the UI, Adobe Target stores extra per-metric state such as:

• whether the metric is `conversion`, `engagement`, or `revenue`
• for conversion metrics, the selected action such as:
  • `Viewed a page`
  • Viewed an mbox`
  • `Clicked on Mbox`

In the browser editor model, this appears as a separate structure like:

"successCriteria": [
  { "metricLocalId": 32767, "successCriteria": "conversion" },
  { "metricLocalId": 1100, "successCriteria": "engagement" },
  { "metricLocalId": 1027, "successCriteria": "conversion" }
]

But the public REST API does not expose this field:

GET /{tenant}/target/activities/ab/{id}

and also rejects it on update:

{
  "errorCode": "InvalidProperty.Json",
  "message": "Invalid Json. Unrecognized property name 'successCriteria'."
}

Why this is a problem

A metric can be configured and valid in the Target UI, but after a REST pull / REST push cycle the public activity representation is incomplete and broken.

Example: an additional metric that was configured in the UI later came back from the REST API as:

{
  "metricLocalId": 1027,
  "name": "Purchases from Specific Users",
  "mboxes": [],
  "clickTrackSelectors": []
}

So the public API no longer contains enough information to recreate the same UI state.

Minimal repro

1. Create or edit an AB activity in the UI.
2. Add an additional metric in Goals & Settings and configure it as:

•    `Conversion`
• `Viewed an mbox`
• choose an mbox

3. Save the activity in the UI.
4. Fetch the activity via REST:

curl -s \
  -H "Authorization: Bearer $TOKEN" \
  -H "x-api-key: $API_KEY" \
  -H "Content-Type: application/vnd.adobe.target.v3+json" \
  "https://mc.adobe.io/$TENANT/target/activities/ab/$ACTIVITY_ID"

5. Observe that the response does not include any public field corresponding to the UI’s metric type selection (`conversion` / `engagement` / `revenue`) such as `successCriteria`.
6. Try to send that field back in a REST update:

curl -s -X PUT \
  -H "Authorization: Bearer $TOKEN" \
  -H "x-api-key: $API_KEY" \
  -H "Content-Type: application/vnd.adobe.target.v3+json" \
  --data '{
    "name": "API repro",
    "successCriteria": [
      { "metricLocalId": 1027, "successCriteria": "conversion" }
    ]
  }' \
  "https://mc.adobe.io/$TENANT/target/activities/ab/$ACTIVITY_ID"

7. REST rejects the field as unknown.

Question

Is the public Admin API expected to fully round-trip AB activity additional metrics created in the UI?

If yes, which documented public field corresponds to the UI’s per-metric type/state?

If no, then the public REST API currently cannot fully preserve AB additional metric configuration used by Goals & Settings.