Configuring custom fields and events

Deep Insights Agent can answer questions about your custom fields and custom events. It uses only the ones you make available. You choose these in the Ometria platform, and your choice applies wherever you use the agent, in both Claude and Microsoft Copilot.

Why this matters

Most organisations hold far more custom fields and events than are useful for analysis. Choosing a focused set keeps answers relevant. It also keeps you in control of what the agent can see.

Select your custom fields and events

To open this page you need permission to view AI settings in Ometria. If you can't see Settings > Deep Insights, check with your Ometria administrator.

1. In Ometria, go to Settings > Deep Insights.
2. Select the custom fields and custom events you want the agent to use.
3. Select Save.

How many you can select

There are limits on how much you can make available to the agent:

• Up to 30 custom fields per category. That's 30 contact fields and 30 order fields, so 60 in total.
• Up to 20 custom event types, and up to 10 properties for each event type.

If you reach a limit, deselect something you no longer need before adding more.

Check for personal data before you save

Keeping personal data out of the agent is your responsibility. Ometria removes any field or event you've tagged as PII, but it can't catch personal data in fields that aren't tagged, so review your selection before you save. For what to look for and how to keep it out, see Keeping personal data out of Deep Insights Agent. The page helps you in two ways:

• Ometria checks the names of the fields you select and lists any that look like they might hold personal data, under a "may contain PII - please verify and remove" note. This is a prompt based on field names, so check each flagged field and remove any that do contain personal data.
• Before you can save, you must tick I confirm that none of the fields or events selected for use in Deep Insights Agent contain PII. The Save button stays inactive until you do.

The name check is a guide, not a guarantee: it can flag a field that's actually fine, and miss one that isn't. A flagged field that holds no personal data is safe to keep, but the final decision is yours.

Good to know

• Your selection is the same whether your team uses Claude or Microsoft Copilot.
• The agent can only see the fields and events you select. Anything you leave out stays hidden from it.
• Ometria excludes any field or event tagged as containing personally identifiable information (PII), for privacy. These don't appear in the selector. You set the PII tag when you set up the custom field or event. For more, see Restricting PII / sensitive data in Ometria.
• Ometria also excludes any field or event that contains HTML, because these are too large to use.
• Beyond those, you decide what's available, so you can keep other sensitive data out of the agent.
• For events that hold a lot of detail, the agent may work from a summary rather than every detail. These events are best for counts and trends.
• New selections should become available in the Deep Insights Agent after the next daily data run.