seeing segment names in custom destination connector

[marc_stowe_za]

hi, I have set up a custom destination server and destination to stream (so not file output) audiences to an end point. In the current payload I can see the audience id from profile.segmentMembership.ups but would prefer to see the audience name.

I see in the destination you can set the paramters

   "segmentMappingConfig": {

    // sets the mapping id in the destination to the segment name

     "mapExperiencePlatformSegmentName":true,

      // sets the mapping id in the destination to the segment id

     "mapExperiencePlatformSegmentId":false,

     // allows the user to map / change the Mapping Id - recommended false

     "mapUserInput":false

   },

and all the documentation says that the name should come through then. it doesnt for some reason

other documentation days you can reference a system generated object destination.segmentAliases[use the key here] and that should return the name for use in the httpTemplate, but that doesnt seem to work either.

has anyone solved this and can help me?

thanks a ton

Marc

[Parvesh_Parmar · Accepted solution]

Hi @marc_stowe_za ,

If I understand correctly, you are building a custom destination using Destination SDK, which you would like to integrate with Adobe Experience Platform (AEP) in order to export audiences from AEP to your destination.

You mentioned a configuration flag that users will set during the destination setup. When this flag is set to true, you expect the segment (audience) name to be exported to your destination.

If you’re building a streaming destination, then yes, this is supported. Based on Adobe’s documentation, you can use the segmentMappingConfig object to control what AEP metadata is mapped:

"segmentMappingConfig": {
  "mapExperiencePlatformSegmentName": true,
  "mapExperiencePlatformSegmentId": false,
  "mapUserInput": false
}

https://experienceleague.adobe.com/en/docs/experience-platform/destinations/destination-sdk/function...

In this case, setting mapExperiencePlatformSegmentName: true will ensure the destination receives the Experience Platform segment (audience) name as the mapping ID during activation.

To implement this properly, you should also define an audience metadata template using the /authoring/audience-templates endpoint and link it in your destination config via the audienceMetadataConfig like this:

"audienceMetadataConfig": {
  "audienceTemplateId": "YOUR_AUDIENCE_TEMPLATE_ID"
}

Important: All parameter names and values are case-sensitive.

While I haven’t personally built a full streaming destination using the SDK, I would recommend checking Adobe’s existing streaming destination examples or built-in destinations (like Meta or Google, Azure event etc) to see how they handle audience metadata mapping. This can give you a working reference to validate your expectations.

You can reach out to Adobe support also. 

Hope it will help you!

Best regards,

Parvesh