Los artículos de ayuda existen en alemán e inglés. Aquí los lees en inglés.
Límites y delimitación
How is Metrunio built technically?
Data is stored and evaluated in PostgreSQL. A BigQuery analytics mirror runs for all accounts; reports are calculated from it once the data volume warrants it. We do not announce future features: what is listed here exists.
Which technical building blocks does Metrunio run on today?
| Topic | Today |
|---|---|
| Queue | PostgreSQL |
| Analytics store | PostgreSQL; a BigQuery mirror runs for all accounts, and reports use it once data volumes are larger |
| Authentication | own session management |
| Bot detection | user-agent heuristic; there is no bot management |
| Platform credentials | via sign-in for Google Ads and Meta, entered by the customer for TikTok, LinkedIn and Microsoft Advertising; stored encrypted |
| GTM template | in the Tag Manager template gallery and as a file from setup |
| Languages | Website and portal complete in German, English, Spanish and French; help articles, emails, weekly report and alerts in German and English, in Spanish and French as the English version |
Note
The BigQuery mirror runs for all accounts; reports only use it once the data volume warrants it. Until then PostgreSQL is simply faster, because no query crosses the network. One exception: if an account keeps raw data for longer than 180 days, its reports come from the mirror, because the measurement database keeps the raw rows of delivered ads for only 180 days. The customer journey list and the single journey stay in PostgreSQL either way: finding a single journey is a different job from summing over millions of rows.
What comes next is decided by customer feedback. We do not publish a list with dates: an announced feature would be a promise that someone factors into their decision.
Revisado por última vez el 15 oct 2026
También se pregunta
- Roadmap
- What comes next?
- BigQuery
Artículos relacionados
- What does Metrunio deliberately not do?
Which features are missing, and why?
No fingerprinting, no marketing mix modelling, no ad server and no consent management of its own. The scope is deliberately narrow: measure, connect, attribute; whatever else you need is done by a tool built for it. There are no extrapolated figures, and every figure says where it comes from, such as measured or attributed.
- Where is the data processed?
Is there a data processing agreement, and where are the servers?
Application, database and analytics storage are planned for the europe-west3 region (Frankfurt); what goes beyond that, such as logs and support access at the cloud provider, is listed in the sub-processor list under “Documents”. You conclude the data processing agreement with us in the portal under “Privacy” or in the Shopify app; nothing is measured before that. We have our own agreements with our sub-processors.
- What does Metrunio cost?
Which plans are there, and what happens if I go over?
Five plans, tiered by events per month: Start (free), Pro (€79), Growth (€249), Scale (€599) and Agency (€299 with two client accounts, €49 per further one, 250,000 events per client account); every four delivered impressions count as one event. Above the allowance, every started 10,000 events cost €3, and a plan never costs more than the next plan up would cost at the same volume.