How to Send Data for Successful Enrichment

Enrichment helps us add extra context and insights to your feedback (for example, themes, sentiment, or metadata). To get the best results, it’s important that the data you send follows a few simple rules.

Written by Kesi Kagbala
February 20, 2026

1. Provide Stable, Unique Identifiers

Each piece of feedback must have a unique ID that never changes.

• This allows us to recognise the same feedback item over time
• It ensures enrichment is applied consistently

Examples:

​feedback_id, review_id, ticket_id

2. Include the Full Text You Want Enriched

Enrichment is based on the raw feedback text.

• Always send the full text (not summaries or shortened versions)
• Avoid modifying historical text unless it has genuinely changed

3. Include Helpful Metadata Where Available

Enrichment is primarily based on the feedback text itself.

However, providing additional metadata can help with:

• organising and filtering feedback in the app
• reporting and segmentation after enrichment
• ensuring feedback is grouped correctly by source

Examples of useful metadata include:

• Language
• Platform or product
• Source (e.g. App Store, Play Store, Support)
• Customer segment or plan (if available)

4. Be Consistent Across Imports

• Use the same field names and formats every time
• Avoid changing schemas after the first import
• Inconsistent schemas can prevent enrichment from running correctly

5. Historical Data & Re-Enrichment

• Enrichment typically runs when data is first ingested
• Previously imported data is not always automatically re-enriched
• If you need historical data enriched or re-processed, let us know so we can advise on what’s possible

Best Practices Checklist

Before sending data, make sure:

• Each feedback item has a stable, unique ID
• Full feedback text is included
• Metadata is consistent and complete
• Field names and formats do not change over time
• You’ve informed us if historical data needs enrichment