.d53b12e5.png&w=3840&q=75 "Trivas.ai")
by Trivas.aiWe're deprecating /resources/data-dictionary. The content isn't going away, but the standalone page is: it's merging into a pillar resource, and the URL will 301 redirect wherever that's viable. A handful of child pages that don't map cleanly to anything in the new structure will get noindexed instead.
Here's the honest reason we're comfortable doing this: over the last three months, this page pulled in under 10 impressions and zero clicks. Nobody was finding it, and almost nobody was landing on it. So this change affects close to no one currently using the site.
Think of this as a cleanup, not a cut. The actual metric definitions, ROAS, CAC, AOV, all of it, still exist. They're just moving somewhere they'll actually get seen.
The dictionary was structured as an index with individual pages underneath it: /resources/data-dictionary/[metric], one page per term. ROAS got its own page. So did CAC, AOV, contribution margin, and a couple dozen others.
Each one was short. A definition, maybe a formula, rarely more than 150 words of actual content. They didn't link to each other in any meaningful way, and almost nothing on the rest of the site linked into them either.
The result was fragmentation: dozens of near-identical, thin pages competing with each other for the same handful of searches, instead of one strong page that could actually rank and actually help someone. It's a pattern a lot of SaaS sites fall into: more pages feels like more content, but it's really just more surface area with less substance per square foot.
The search data makes the case on its own. Near-zero impressions for a generic "data dictionary" index means there's no real query volume pointing at it. People aren't searching "ecommerce data dictionary" and landing here. They're searching for specific things, "what is ROAS," "CAC formula," and a disconnected index page isn't built to catch that.
There's a second cost too. A big batch of thin, low-value pages doesn't just sit there neutrally. Search engines evaluate quality signals in aggregate across a site, and a pile of near-duplicate definition pages with no backlinks and no internal linking drags down how the rest of the site gets assessed. It's dead weight.
Compare that to what happens when the same definitions live inside a page that already has topical authority, something covering dashboards, reporting workflows, and analytics decisions end to end. That page already earns backlinks and already ranks for related terms. A metric definition embedded in it inherits some of that authority instead of starting from zero on its own.
The consolidation target is guides and reports. Metric definitions are folding into a reference section inside a broader analytics guide there, rather than living as orphaned standalone pages.
This makes sense structurally. That hub already covers how dashboards get built and how reporting actually works day to day. A definition of contribution margin means more next to a walkthrough of how it shows up in a report than it does sitting alone on a page with nothing around it.
Where a definition is tightly tied to how a metric actually renders on a dashboard (how ROAS gets sliced across ad platforms, say), we're cross-referencing it from dashboards and analytics help too. That way the definition and the mechanics live next to each other instead of forcing someone to hop between two unrelated corners of the site.
Here's the mechanical plan, in order:
None of this is exotic. It's the standard checklist for retiring a low-performing page without losing whatever thin value it had.
If you came here looking for a definition, the short answer is: it's not gone, it just moved.
Head to guides and reports for the consolidated definitions, now with the context of how each metric actually shows up in reporting rather than a bare formula on an island.
If what you actually need is how a metric behaves inside a specific dashboard view, say, how ROAS gets calculated differently across Amazon, Shopify, and Meta, that's covered in the dashboards and analytics help section, not the guide itself.
Nothing here got deleted. It just stopped being split across dozens of thin, disconnected pages that nobody was finding anyway.
A definition on its own is only so useful. Knowing that ROAS equals ad revenue divided by ad spend doesn't tell you much if you can't see it move in real time across the channels actually driving your spend.
That's the gap a static dictionary page can never close, and it's the whole premise behind Trivas's BI reporting: these metrics get calculated automatically, pulled live across Amazon, Shopify, and your ad platforms, instead of something you look up on a page and then go calculate yourself in a spreadsheet.
If you want to keep tabs on how we're restructuring resources like this one, or just want more on how to actually use these metrics rather than just define them, the blog is where that shows up first.
explore more insights
3 min read
3 min read
3 min read