Adobe Target

Datafly Signal records Adobe Target order conversions server-side through the Delivery API: each order is an execute request for your order-confirmation mbox carrying the order id, total and product ids, so activities and Recommendations that use that mbox record the conversion and revenue.

⚠️

Cannot deliver yet. The Delivery API requires a sessionId query parameter that stays the same for a visitor for 30 minutes. Signal’s delivery URL cannot carry a per-visitor value until #1283 lands, so requests are refused until then.

Why route Adobe Target through Datafly Signal

Events arrive when the browser cannot send them. Server-side delivery is not stopped by ad blockers, tracking prevention or a page unload.
One consent decision governs every destination. The integration is gated by the same consent state as the rest of your stack.

Prerequisites

Your Adobe Target client code (Administration > Implementation).
An order-confirmation mbox used by your activities (for example orderConfirmPage).
Signal capturing the visitor’s Target id (the PC value of the mbox cookie) as adobe_tnt_id, or the Experience Cloud ID.

Configuration

Field	Required	Description
`client_code`	Yes	Your Adobe Target clientCode (also called the tenant or client). Find it in Target under Administration > Implementation. It forms the API host (CLIENTCODE.tt.omtrdc.net) and the mandatory client query parameter. No API key is required: the Delivery API is unauthenticated and scoped by this code.
`mbox_name`	Yes	The mbox that records orders, the one your activities and Recommendations use as the order confirmation (for example orderConfirmPage). Each order is sent as an execute request for this mbox with the order id, total and product ids.

Configure in Signal

Add the integration

Go to Integrations > Add Integration > Adobe Target.

Choose a preset

Default: order conversions.

Enter the configuration

Fill in the fields in the table above.

Choose the categories that gate personalisation for your site.

Save

Signal delivers the next matching event.

API Endpoint

POST https://CLIENT_CODE.tt.omtrdc.net/rest/v1/delivery?client=CLIENT_CODE&sessionId=SESSION_ID
Content-Type: application/json

No API key: the client code scopes the request. sessionId is required by Adobe and is not yet sent (see above).

Identity Signals

Signal	Sent as	Notes
Target visitor id	`id.tntId`	From `collected_ids.adobe_tnt_id`.
Experience Cloud ID	`id.marketingCloudVisitorId`	From `vendor_ids.ecid`. An order with neither id is not sent.

Event Mapping

Default preset (`default`)

Server-side order conversions for Adobe Target: each order is an execute request for the configured order-confirmation mbox carrying order.id, order.total and order.purchasedProductIds, so activities and Recommendations that use that mbox record the conversion and revenue. The visitor is the durable tntId (collected_ids.adobe_tnt_id, from the mbox cookie) and/or the Experience Cloud ID (vendor_ids.ecid); an event with neither is not sent. CANNOT DELIVER YET: the Delivery API requires a sessionId query parameter that stays the same for a visitor for 30 minutes, and the delivery URL cannot carry a per-event value until #1283 lands. Page views are not sent: a display notification needs the event token from the browser’s prefetch, which a server-side forwarder does not have.

Signal event	Sent as	Enabled
`purchase`	`orderConfirm`	Yes

To customise, edit the integration’s Field Mappings in the Management UI.

Example: an order

What Signal sends (rendered from the preset):

POST https://acmecorp.tt.omtrdc.net/rest/v1/delivery?client=acmecorp

{
  "context": {
    "address": {
      "referringUrl": "https://www.google.com/",
      "url": "https://www.example.co.uk/shop/jackets?utm_source=google"
    },
    "channel": "web",
    "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7)"
  },
  "execute": {
    "mboxes": [
      {
        "index": 0,
        "name": "orderConfirmPage",
        "order": {
          "id": "T-1001",
          "purchasedProductIds": [
            "SKU-1",
            "SKU-2"
          ],
          "total": 279.98
        }
      }
    ]
  },
  "id": {
    "tntId": "abcdefghijkl00023.1_1"
  }
}

Testing

Send a test event

Trigger the event on your site, or replay one from Signal’s event debugger.

Check the response

Once #1283 lands, confirm a 2xx response and check the conversion in the activity report for the order mbox.

Troubleshooting

Problem	Solution
Requests refused	Expected until #1283: the Delivery API requires `sessionId`.
Order not attributed	The order mbox must be the one your activities use as the conversion.

Limitations

Page views are not sent: a display notification needs the event token returned by the browser’s prefetch.
Product views for Recommendations (entity.id parameters) are not sent: the parameter names contain dots, which a mapping target cannot express.

Dynamic Yield Kameleoon