audience name as output in custom destination connector | Community
Skip to main content
M
marc_stowe_za
Level 3
May 25, 2025
Question

audience name as output in custom destination connector

  • May 25, 2025
  • 2 replies
  • 549 views

hi, are there any bright spraks out there who know how to include the audience name when creating a custom streaming destination?

 

I see the template in the destination server uses the segmentmembership.ups object , so as an example:

 

{%- for segment in profile.segmentMembership.ups | added %}
{ "Email": "{{ identity.id }}",
"SegmentId": "{{ segment.key }}",
"Status": "{{ segment.value.status }}",
"QualTime": "{{ segment.value.lastQualificationTime }}"
}
{%- endfor %}

 

but I'm really looking to do is rather use the more useful audience name as opposed to the guid id


{ "Email": "{{ identity.id }}",
"SegmentName": "{{ The name of the segment }}",
"Status": "{{ segment.value.status }}",
"QualTime": "{{ segment.value.lastQualificationTime }}"
}

 

so looking at the profile api fior entities, i see as part of the payload:

"segmentMembership": {
                "ups": {
                    "61453783-8d59-4153-b202-d05ee": {
                        "status": "realized",
                        "lastQualificationTime": "2025-03-04T08:06:03Z"
                    },
 
which makes sense, but how do i link the name of the actual segment / audience in the destination server template?
 
hoping for enlightment 🙂
Marc

 

2 replies

Asheesh_Pandey
Community Advisor
Asheesh_PandeyCommunity Advisor
Community Advisor
May 25, 2025

@marc_stowe_za 

1. You can transform template and use destination.namespaceSegmentNames, to adds a lookup of segment names for each segmentMembership.ups GUID in the payload sent to your destination. 

How to Enable - in you destination server configuration set the flag as true

2. on UI by configuring destination, edit "File name" and then Append settings to enable "Segment name". How to append various settings

 

    M
    marc_stowe_zaAuthor
    Level 3
    May 26, 2025

    Hi

     

    thanks for the reply. I need to stress this is a streaming connection, so can't use the UI to influence a filename, it needs to be embedded in the json object.

     

    for option 1 , are you saying that I would need to build a decode type of lookup where I say something like guid xyz = audience name 1? 

     

    regards

    Asheesh_Pandey
    Community Advisor
    Asheesh_PandeyCommunity Advisor
    Community Advisor
    May 27, 2025

    @marc_stowe_za Nope! you don't need to create a lookup table to the destination with segment id and segment name (However, that is another option). I see you also working on it (another thread) with 

      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      July 2, 2025

      @marc_stowe_za Just checking in — were you able to resolve your issue?
      We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!

      Kautuk Sahni
      Terms & ConditionsAccessibility statement

      Loading footer...