Skip to main content
When your SDK sends custom metadata with conversations, OpenBat auto-discovers those fields. You can then choose to track them, making them available as filters in the conversations table.

​
How metadata discovery works

  1. Your SDK sends conversations with metadata (e.g., plan, industry, mrr)
  2. OpenBat detects new metadata keys it hasn’t seen before
  3. New keys appear in the Discovered fields table on the Metadata tab
  4. You choose to Track, Accept, or Deny each field

​
Track metadata fields

1

Send metadata from your SDK

Include metadata in your conversation payloads. See Install the SDK for examples.
await client.conversations.create({
  messages: [...],
  metadata: {
    userId: 'user_123',
    email: 'user@example.com',
    plan: 'enterprise',
    mrr: 499,
    industry: 'Developer Tools',
  },
});
2

Navigate to the metadata tab

Go to /platform/{chatbotId}/analysis-config and stay on the Metadata tab.
3

Review discovered fields

New fields appear in the Discovered fields table. Common auto-discovered fields include:
FieldSource
browserSDK session context
deviceSDK session context
ipRequest metadata
languageBrowser language
osOperating system
refererReferring URL
userAgentBrowser user agent
4

Track or deny each field

For each discovered field:
  • Click + Track to add it to managed fields (makes it available as a conversation filter)
  • Click Accept to acknowledge without tracking
  • Click Deny to reject the field
Tracked fields move from Discovered fields to Managed fields and become available as filter columns in the conversations table.
Track fields you actively want to filter and segment by. Deny fields you don’t need to keep the interface clean and focused.

​
Next steps

Analysis configuration

Explore all configuration options.

Conversations

Filter conversations using your tracked metadata fields.