When metric misalignment costs more than the meeting

Custom Metrics extends Fospha's trusted measurement to every stakeholder conversation - eliminating the translation tax that slows budget decisions.

A retail CMO once told us their quarterly board meeting was derailed in the first 15 minutes.

Finance questioned why marketing's ROAS calculations didn't match the numbers they had prepared. Both teams were working from Fospha data. The measurement was identical. The problem wasn't the source - it was the translation.

Finance had calculated Cost of Sale as Cost / Revenue.

Marketing had calculated it as Cost / (Revenue - Returns).

Both formulas were defensible. Neither team realized the other had made a different choice. An hour was spent reconciling definitions instead of discussing growth strategy.

"That's when we realized," the CMO said, "every spreadsheet between our measurement and our stakeholders was a point of failure."

This is the translation tax. And it compounds faster than most organizations realize.

Why does metric version drift happen?

Six people start the quarter with the same Cost per Visit formula in their spreadsheets. By Q3, they're working from six different versions.

Someone excludes returns. Someone adjusts for shipping. Someone switches from monthly to weekly calculation. No one documents the change. No one realizes the drift is happening.

By the time leadership asks, "What's our Cost per Visit?" there are multiple answers and no clear source of truth.

The problem isn't the people maintaining those spreadsheets. It's the architecture itself.

Any step that requires a spreadsheet between your measurement platform and a stakeholder decision is a step that introduces the possibility of drift.

In modern retail, that drift has real costs:

- Budget conversations stall on "Whose numbers are we using?"

- Trust between marketing and finance erodes gradually

- Time spent reconciling formulas instead of acting on insights

- Investment decisions delayed by definitional debates

The operational cost isn't dramatic in a single meeting. It accumulates over time - meeting after meeting, quarter after quarter - until the friction between measurement and decision-making becomes the invisible governor on organizational speed.

The translation tax is an industry-wide pattern. Measurement platforms produce trusted data. Stakeholders need that data expressed in their language -Cost of Sale, Revenue per Visit, Conversion Rate. The spreadsheet becomes the translation layer. And then it multiplies.

This is what Custom Metrics is designed to eliminate.

How does Custom Metrics extend Fospha's Measurement OS?

Fospha already measures incrementality accurately at the channel level across paid social, paid search, display, affiliate, and every touchpoint that drives performance. That measurement is trusted by the marketing teams who use it daily to optimize spend.

Custom Metrics extends the reach of that trusted measurement to the stakeholders who need to act on it: finance teams who think in Cost of Sale, commercial leadership who allocate budgets based on Revenue per Visit, and retail teams who track Conversion Rate.

The extension happens inside the platform. An Admin defines the KPI once - combining the measurements Fospha already tracks (Revenue, Cost, Visits) using simple math (add, subtract, multiply, divide) - and it calculates automatically for every user, every channel, every day. No export required. No formula to maintain in six different spreadsheets. No version to reconcile before the meeting.

This is how trusted measurement becomes organization-wide measurement. Custom Metrics is the layer that completes the loop - from Fospha's incrementality model to the KPI language every stakeholder already speaks.

What problems does Custom Metrics solve?

Custom Metrics lets you build the KPIs your organization runs on - Cost of Sale, Revenue per Visit, Conversion Rate, or any metric your business needs - directly inside Fospha using a no-code formula builder.

Here's what changes:

- Define once, calculate everywhere. Build Cost of Sale as Cost / Revenue in Fospha's settings. It appears automatically for all users across Channel Health Check, Reporting, Optimization, and exports.

- It refreshes daily. As Fospha's measurement updates, so do your custom metrics. Marketing, finance, and commercial leadership see the same number at the same time.

- No translation layer. The KPI lives in the platform - not in six spreadsheets maintained by six different people with six different interpretations.

Return to that board meeting. The CMO whose quarterly review was derailed by a Cost of Sale definition debate is now working with pre-agreed KPIs that refresh daily from the same measurement system. Finance sees their metrics. Marketing sees theirs. Both are calculated the same way, sourced from the same place.

The meeting is back to being a strategy conversation.

One clarification: Custom Metrics is a reporting feature. It combines Fospha's base metrics into your organization's KPI language. It does not modify attribution logic, MMM methodology, or incrementality modeling. The measurement stays the same. What changes is how that measurement reaches your stakeholders.

Return to the board meeting

The CMO whose quarterly review was derailed by a Cost of Sale definition debate is now working with pre-agreed KPIs that refresh daily from the same measurement system. Finance sees their metrics. Marketing sees theirs. Both calculated the same way, sourced from the same place.The meeting is back to being a strategy conversation.

That is what changes when the metric is pre-agreed: the conversation starts at the decision, not the definition. Finance sees Cost of Sale and Revenue per Visit in the format they recognise, refreshed daily, no reconciliation meeting required. Commercial leadership allocates budget from a shared commercial reality. Channel managers stop spending three hours a week exporting, calculating, and reformatting data that the platform already knows how to produce.

When measurement becomes infrastructure

The organisations winning in retail commerce are the ones where measurement has stopped being a reporting function and started shaping how decisions get made. Where marketing, finance, and retail teams operate from the same system - in real time, with no translation step between insight and action. Where measurement is integrated deeply enough into the commercial engine that budget allocation, creative optimisation, and financial forecasting all pull from the same source.That is the Measurement OS. Not just accurate measurement - but measurement trusted enough, and integrated completely enough, to become the foundation for every decision that matters.Custom Metrics is the release that extends it across your organisation.

Custom Metrics is live in Fospha today.

Build your first metric in Settings → Custom Metrics. If there's a KPI your team currently calculates outside the platform, start there. Define it once. Let everyone work from the same number.

👉 Create your first Custom Metric

Setup guide: https://help.fospha.com/en/articles/13862974-how-to-build-custom-metrics

‍

Frequently Asked Questions

1. What is Custom Metrics in Fospha?

‍Custom Metrics is a reporting feature that lets you define your organization's KPIs directly in the Fospha platform using a no-code formula builder. It combines Fospha's base metrics (Revenue, Cost, Visits, Conversions, etc.) into the KPIs your stakeholders need—like Cost of Sale or Revenue per Visit.

2. How many custom metrics can I create?

‍Each organization can create up to 10 custom metrics. Once created by an Admin, they appear automatically for all users across Channel Health Check, Reporting, Optimization, and CSV exports.

3. Who can create and view custom metrics?

‍Only Admin users can create, edit, or delete custom metrics. However, once created, all users in your organization can view them in their dashboards and reports.

Does Custom Metrics change how Fospha measures attribution?

‍No. Custom Metrics is a reporting feature, not a measurement methodology change. It combines Fospha's existing base metrics into your organization's KPI language. It does not modify attribution logic, MMM methodology, or incrementality modeling.

What types of custom metrics can I create in Fospha?

Custom Metrics combines any of Fospha's base metrics—Revenue, Cost, Visits, Conversions, Impressions, Clicks—using standard operators (+, –, ×, ÷, parentheses).