What a custom metric calculates, which fields you can use in it, and when SEINō works it out
Say you want a metric like Revenue per send, and your dataset doesn’t have it. It does have revenue, and it does have sends. A custom metric turns those into the number you want: a custom field that calculates it from fields your dataset already has.
Once you save it, you can use it like any other metric: in the data explorer, dashboard widgets, alerts, and target plans.
What you can put in an expression
Section titled “What you can put in an expression”An expression is a calculation. You can add, subtract, multiply, and divide. Brackets group parts of it, and plain numbers are allowed too, such as dividing by 1000.
You can only use fields that add up. Revenue, Sent, and Transactions work like this: add two campaigns together and the total still makes sense.
Rates and averages don’t work like this. An open rate is already a division. Add the open rate of two campaigns together and the answer means nothing.
That’s why SEINō doesn’t offer these fields while you type. Use the totals behind them instead: for an open rate, divide Open by Sent.
The same rule covers custom metrics you made earlier. One that adds or multiplies can be used again. One that divides can’t.
Why the order of your fields matters
Section titled “Why the order of your fields matters”A custom metric can only use the custom fields above it in the field list, not the ones below. Fields that come from your integrations are always available, wherever they sit.
This explains two things you may notice. A custom field sometimes won’t move when you drag it past another one. And a metric you made a moment ago isn’t offered to a metric above it.
When SEINō calculates a custom metric
Section titled “When SEINō calculates a custom metric”SEINō calculates a custom metric when a report runs, not when you save it. The number isn’t stored anywhere.
A new metric covers your whole history straight away. If a number looks wrong, correct the expression and run the report again.
Next: Add a custom dimension to see how a custom field is built and saved in the Data model editor.