A custom field is a field you add to a dataset yourself, alongside the ones your integrations supply. There are two kinds: a custom dimension you slice by, and a custom metric you measure. They exist so your reporting can follow the categories and numbers your business already works with (a campaign theme, a lifecycle stage, revenue per subscriber), not only the ones your integrations happen to send.
Where custom fields live
Section titled “Where custom fields live”A custom field belongs to one dataset in one workspace, so two workspaces can hold the same dataset and see different fields. Custom fields live in Workspace settings under Data model, open to workspace admins, so ask an admin if you don’t see it. Once saved, a custom field behaves like any supplied field: pick it in the data explorer, dashboard widgets, alerts, and target plans. SEINō calculates a custom field when a report runs, so a new or edited field applies to your full history straight away.
Custom dimensions
Section titled “Custom dimensions”A custom dimension sorts your data into categories you define, so you can group a metric by something your source data doesn’t carry. You build one from rules: each rule tests a field and assigns a result, and a default catches everything no rule matched. You might map a country code to a sales region, or sort campaign names into a channel, so that every name containing “newsletter” becomes Newsletter. See Add a custom dimension for the steps.
Custom metrics
Section titled “Custom metrics”A custom metric calculates a number from fields the dataset already has. You write it as an expression using addition, subtraction, multiplication, and division: revenue divided by sends gives you revenue per send. An expression can only reference fields that add up, so it builds on totals like revenue or sends rather than on rates. See Custom metrics for what you can put in an expression.
Why rule order matters
Section titled “Why rule order matters”SEINō reads a custom dimension’s rules from the top and stops at the first match, so their order changes the answer. A rule catching “sale” above a rule catching “summer sale” means the second never runs, and every summer sale campaign lands in the broader bucket. Put the most specific rules first. Order also governs what a field can build on: a custom field can only reference custom fields above it, which is why some fields won’t drag past others.
What custom fields can’t change
Section titled “What custom fields can’t change”Custom fields add to a dataset; they don’t rewrite it. The fields your integrations supply stay as they are: you can’t rename, hide, or delete them, and a custom field never overwrites their values. When a supplied field is close but not quite right, add a custom field that reads from it and leaves the original intact.