Hi Cortney! That's helpful information -- and honestly points to this being a limitation of the underlying dataset rather than the widget configuration.

As for native links, the answer is maybe, depending on the channel and reporting dataset. Some datasets expose fields such as Permalink, Message URL, Source URL, or Native URL that can be added to exports, while others don't make those fields available in reporting. Unfortunately, availability varies quite a bit by source.

Could you share:

• Which social/community channel the messages are coming from?
• Which reporting widget or reporting dataset you're using?

With that information, we can determine whether a native URL field is available and, if not, whether there's an alternate export method that includes the link back to the original post/comment.

Curious to hear what source you're pulling from! 😊

Instead, you’ll want to use a Message Level Reporting widget and select the Message dimension.

• The Inbound Message dimension often includes additional context (like sender profile), which is why you’re seeing both name + text
• The Message dimension (within Message Level Reporting) is designed to return just the message body

How to do it:

• Use a Message Level Reporting widget
• Select Message as the dimension (instead of Inbound Message)
• Add a filter like Message Sent By = Fan/Customer to keep only inbound content

This should give you the clean text-only output you're looking for.