Quelle tâche souhaitez-vous accomplir ?

• What is Metrunio?

  What does Metrunio do, and who is it for?

  Metrunio shows you which measured ad contacts preceded your orders or leads, and distributes revenue by a rule you can see and change. It measures clicks, visits and conversions with its own signals and, wherever your own tag is served, the delivery and viewability of ads as well. It is built for shops, agencies and SaaS businesses that allocate ad budget and need a source that is not owned by the platform being advertised on.

• Setup: six phases, eleven steps

  What do I have to do before the first data arrives?

  The setup assistant takes you through six phases, from “Company & DPA” to “Check the first journey”; behind them are eleven steps, the same for every integration route. The second step is concluding the data processing agreement, without which nothing is measured. The assistant saves progress automatically and can be interrupted at any time; going live also needs access to the ad accounts, the connection to your consent tool and, depending on your company, internal approvals.

• How do I connect Google Tag Manager?

  How do I install Metrunio through Google Tag Manager?

  You add the “Metrunio Tracking” template from the Tag Manager template gallery or download it as a file in “Setup”. You create a tag from it, enter site ID and write key, choose the trigger “Initialization - All Pages” and publish. This route needs no change to your website’s source code.

• No data after setup? Check these six points

  No data arrives after installation. What do I check?

  First: is the data processing agreement concluded? Without it Metrunio accepts nothing, and the portal shows “Measurement paused: DPA missing.”. If it is concluded, the GTM container is usually not published, consent is missing or the domain is not in the allowed list; these six steps cover the most common causes.

• How do the attribution models calculate?

  Which models exist and how do they distribute the share?

  There are seven models: six distribute a conversion by a fixed, disclosed rule, and the seventh reads the rule from your own paths. If a model finds matching touchpoints, it distributes the conversion’s full value across them; if it finds none, the conversion stays “unattributed” and is shown separately. Attributed and unattributed together add up to all conversions it calculates.

• What happens without consent?

  Is nothing really stored without consent?

  By default, Metrunio stores nothing without matching consent, not even a raw event, and the tracking script sends nothing before a decision. One documented case differs: purchases and refunds your server reports without consent count towards measured revenue for revenue reconciliation, with their order number and without browser, customer or advertising identifiers, and are not attributed. After a refusal this only applies with an activated additional instruction. Without consent on the ad side, the click redirect passes on only the campaign, no click ID.

• Why do my numbers differ from Meta and Google?

  Metrunio shows fewer conversions than the ad account. Why is that?

  Deviations are normal and usually explainable: different attribution windows, different models, the same conversion claimed by several platforms, and missing signals where consent was not given. Metrunio counts each purchase once, even when browser and server report the same order, and distributes it by a rule you can inspect.

• How do I handle access, deletion and objection?

  A data subject exercises their rights. What do I do?

  Privacy requests are handled in the portal under “Privacy”, not by ticket. Every request is recorded and logged in the change log; the data subject is located through a pseudonymous identifier.

• 01

  Fondamentaux

  Ce que mesure Metrunio, en quoi il diffère de l'analytics web et quels termes nous employons.

  7 articles

• 02

  Démarrage et compte

  Inscription, assistant de configuration, premier site web, premières données.

  13 articles

• 03

  Installation

  Google Tag Manager, extrait de code, applications et plugins de boutique, API d'événements serveur et le SDK de suivi.

  25 articles

• 04

  Consentement

  Relier les outils de consentement, comportement avant le consentement, test de consentement.

  7 articles

• 05

  Campagnes et mesure

  Clic, impression, visibilité, éléments de suivi et macros.

  13 articles

• 06

  Parcours et identités

  Comment les signaux deviennent un parcours et quels identifiants y sont reliés.

  7 articles

• 07

  Attribution

  Les sept modèles, fenêtres temporelles, post-view et la comparaison des modèles.

  10 articles

• 08

  Rapports, coûts et export

  Analyses, coûts publicitaires, renvoi vers les plateformes, export CSV et le chat.

  32 articles

• 09

  Qualité des données et dépannage

  Diagnostic, codes d'erreur, données manquantes et ce qui y remédie.

  7 articles

• 10

  Protection des données et sécurité

  Ce qui est enregistré, ce qui ne l’est pas, droits des personnes et conservation.

  13 articles

• 11

  Utilisateurs, rôles et formules

  Accès, autorisations, quota d'événements et support.

  21 articles

• 12

  Limites et périmètre

  Ce que Metrunio ne fait volontairement pas et où la mesure s'arrête.

  7 articles

• llms.txt

  Index bref de tous les articles

• llms-full.txt

  Texte intégral de tous les articles

• /api/knowledge-base

  Articles et sections au format JSON

Si une question manque ici, elle manque au centre d’aide et non à vous. Écrivez-nous via « Demander un appel ».

Demander un appel