Skip navigation links
Digital Experience Studio > Social Media > Sprinklr > Analytics and Research >

Message Metadata

Message Metadata

What is Metadata?

Metadata is a term used to describe the fields or attributes used to describe content. In the context of Sprinklr, metadata can help track information that is important for measurement and content strategy.

There are four main categories of metadata involved with Sprinklr:

  • Message properties
  • University-level custom fields
  • Unit-level custom fields
  • Campaigns

Read more about these types of metadata on the tabs below.

Types of Metadata

Message properties refer to characteristics and classifications of a message in Sprinklr. These are typically applied automatically by Sprinklr or because of some action taken in Sprinklr. Below are a few message properties to be aware of:

  • Status: This is an indication of whether a message has been processed. Utilizing the macros in the customer service workflow (see Engagement Workflows) adjusts the status automatically as messages are processed.  
  • Message Queues: These are the queues (lists used for message processing workflows) that the message is assigned to, at the unit and university level.  
  • Spam: This is an indication that the message has been marked as spam in Sprinklr. This does not mark the message as spam on the native social channel.
  • Sentiment: Sprinklr will automatically score a message as positive, negative or neutral. This is set automatically but can be manually overridden to change the score. AI scoring is often inaccurate, particularly in cases of sarcasm or when context changes the meaning of a message.  
  • Influencer Index: This indicates how much influence that specific profile has on other users. Sprinklr has not clarified how this is calculated.
  • Spam Index: This indicates how often a profile posts spam. Sprinklr has not clarified how this is calculated.
  • Participation Index: This indicates how often a profile interacts with MSU accounts. Sprinklr has not clarified how this is calculated.​ 

Using Metadata

There are a few guidelines when selecting custom fields:

  • Don’t create tags and measurements for the sake of measurement. Each tag adds another step to the posting process. If the unit won’t report on the tags and put the information to use, the unit shouldn’t include them in their workflow.
  • Keep tags as broad and inclusive as possible while ensuring they’re specific enough to provide valuable information. For example, for a story campaign that changes monthly, the tag can be “Monthly Story Feature” instead of the specific story name. The goal is to have a set of flexible tags that meet needs without having to constantly edit the set of tags.
  • University Communications and Marketing can control the visibility of tags based on selections for other tags. So, for example, if the unit has a set of campaigns that change every year, University Communications and Marketing can program the system so that users first select a fiscal year and, depending on the year selected, the appropriate campaign options appear for selection in the next step.
  • Custom fields can be created so that one or many options can be selected. We’ll need to know if it’s possible to select more than one option for a field before it is created. 
  • University Communications and Marketing recommends that units make all fields required fields. This way units can ensure all posts are properly tagged and, therefore, the unit reporting using these fields is more accurate. 

Documentation updated: Nov. 1, 2024

Analytics and Research