Each Moderation Dashboard application has different moderation policies and custom moderation workflows that are platform specific. Sending metadata in the API request along with your content will help you tailor the perfect moderation workflow specific to your company's application.

Overview

You can use Metadata to:

View additional content and user details while moderating tasks in the Review Feed
Create automated rules that incorporate your metadata
Create Review Feed filters to route specific tasks to their own feed

There are 2 types of metadata supported on Moderation Dashboard. Both content metadata and user metadata can be submitted as a JSON object in the API request (refer to v2 - Moderation Dashboard API Reference).

Field	Type	Description
content_metadata	JSON Object	Associated with any post on a platform. For example, a customer may use content metadata to differentiate moderation policies between story posts and feed posts on a platform. View this metadata on Moderation Dashboard when you click into a piece of content. JSON Limit: 2000 lines
user_metadata	JSON Object	Associated with a specific user on the platform. Tied to each user ID on Moderation Dashboard, which is sent with every API request. For example, a customer may use user metadata to differentiate between verified v.s. non-verified users on their platform. View this metadata on the Moderation Dashboard when you open the User Detailed View. Note: We save user IDs. If the user ID is changed with a new submission, we will overwrite the old saved user ID with the new user ID. JSON Limit: 2000 lines

Field

Type

Description

content_metadata

JSON Object

Associated with any post on a platform. For example, a customer may use content metadata to differentiate moderation policies between story posts and feed posts on a platform.

View this metadata on Moderation Dashboard when you click into a piece of content.

JSON Limit: 2000 lines

user_metadata

JSON Object

Associated with a specific user on the platform. Tied to each user ID on Moderation Dashboard, which is sent with every API request. For example, a customer may use user metadata to differentiate between verified v.s. non-verified users on their platform.

View this metadata on the Moderation Dashboard when you open the User Detailed View.

Note: We save user IDs. If the user ID is changed with a new submission, we will overwrite the old saved user ID with the new user ID.

JSON Limit: 2000 lines

View Metadata on the Dashboard

Content Metadata

Displayed when a moderator clicks into a content to view more details in the Post Review Feed or the User Content page.

There are two view options:

Raw: Raw JSON metadata.
Structured: Extracts the JSON metadata out in a cleaner, more user-friendly view. They will be displayed in the order configured in the Settings page.

Content metadata displayed in the Content Detailed View

User Metadata

Displayed when a moderator clicks into a user to view more details in the User Review Feed or the Users page.

Configure Metadata

To display metadata on the Dashboard in JSON format, you don't need to configure metadata. However, in order to create rules that incorporate your metadata, or view metadata in the “structured” table of the content detail view, you will need to first configure your metadata on the Settings page, under API Fields Config.

For each metadata field, you will need to specify:

Display Name
Metadata Type (content, user)
Path to Value (JSON dot-notation to specify exact path to the value)
Value Type (metadata value type - text string, boolean, number, IP address)

For more information on moderation rules, refer to the Defining Moderation Rules page.

Example Metadata Config & JSON

Display Name	Metadata Type	Path to Value	Value Type
Lifetime Revenue	Content	user.lifetime_rev	Number
Environment	Content	environment	Text String

{
  "environment": "prod",
  "user": {
    "lifetime_rev": "452",
    "location": "San Francisco, California"
  }
}

Create Metadata Rules

Once you have your metadata configured, you can create metadata rules on the Rules page.

Example Post Rule: "IF Post triggers any of the following Moderation Categories (Luxury Brands) AND Content Metadata Field (Item Price) is <= 500, THEN Flag Post for Review"