Ir al contenido

Los artículos de ayuda existen en alemán e inglés. Aquí los lees en inglés.

Atribución

How do I ask customers after a purchase how they found me?

With the post-purchase question, on every plan. You switch it on under “Settings → Measurement rules” and call metrunio.renderSurvey() with the order number on your thank-you page. The answers appear as “self-reported” under “Channels & attribution”: next to what is measured, never in revenue and never in an attribution.

Can Metrunio ask after a purchase how someone heard about us?

Some routes to you leave no signal: a podcast, a recommendation from a friend, a poster, an answer from ChatGPT. Measurement then only sees the purchase, and it stays unattributed. The post-purchase question collects the missing information where someone can give it: on the thank-you page, with the question “How did you hear about us?”.

Setting it up

  1. 01Switch on the answers under “Settings → Measurement rules → Post-purchase question”. Until then, Metrunio rejects them.
  2. 02On your thank-you page, after the tracking code, add a placeholder and call metrunio.renderSurvey() with the order number. The example is below and in the portal.
  3. 03Place a test order and answer the question. The answer then appears under “Channels & attribution” and in the order’s journey.
<div id="metrunio-frage"></div>
<script>
  metrunio.renderSurvey('#metrunio-frage', { orderId: '10045' });
</script>
  • The order number must be the same as for the purchase. Only then does the answer sit next to the measured purchase.
  • If you add Metrunio through Google Tag Manager, queue the call instead of making it directly: (window.metrunioQueue = window.metrunioQueue || []).push(['renderSurvey', '#metrunio-frage', { orderId: '10045' }]);. It runs as soon as the SDK has loaded.
  • Use answers to narrow the list, for example answers: ['podcast_radio', 'recommendation', 'search', 'other']. The order stays that of the fixed list.
  • The language follows the page’s lang or the locale option: German, English, Spanish or French.
  • The widget uses the informal address, as Metrunio does. If your shop addresses customers formally, set formal: true: in German it then asks “Wie haben Sie von uns erfahren?”, and in Spanish it uses “usted”. English has no difference; French is always formal.
  • The widget takes on your page’s font and colour. Adjust it with the classes metrunio-survey, metrunio-survey-question and metrunio-survey-answer.
  • If your thank-you page already asks its own question, report the answer with metrunio.survey({ orderId, answer }). answer is a key from the list below.

The answers

KeyAnswer on the page
searchSearch engine, such as Google
socialInstagram, Facebook or TikTok
videoYouTube
recommendationRecommendation from friends or acquaintances
podcast_radioPodcast or radio
tvTV
newsletterNewsletter
influencerInfluencer or blog
ai_assistantChatGPT or another AI assistant
printNewspaper, magazine or poster
returningI have been shopping here for a while
otherOther

Note

There is no free-text field. “Other” is an answer without input: in free fields, people write names, addresses and complaints about the delivery, and none of that belongs in your measurement data.

What the report shows

  • Per answer, how often it was given and its share of all answers.
  • The answer rate: answers relative to the measured purchases in the period. With ten answers, a share of 40 percent says little; that is why the rate is always shown.
  • Per answer, how many of those purchases are attributed, how many are not, and how many answers match no measured purchase. This shows whether “podcast” turns up where measurement found nothing.
  • An order’s journey shows the answer as a line of its own.
  • In the chat and via MCP you query the same figures, with the same label.

The answers are labelled “self-reported”. That someone answered is measured; what they say is their own account. They never appear in revenue, in an attribution or in any model, and they are not extrapolated to the purchases without an answer. A self-report is not a measured touchpoint: someone who says “podcast” may also have seen an ad.

Consent and retention

  • Only with consent to analytics. Without it, the widget shows nothing rather than asking for an answer that would not arrive; metrunio.survey() discards it.
  • One answer per order. The first one counts; a second one for the same order number is not stored.
  • The answer is attached to the event it arrived with. When the retention period ends, when someone withdraws consent or when you delete a person’s data, it goes too.

What you tell your customers

The post-purchase question is not an anonymous survey. The answer is stored with the order number and the browser’s visitor identifier, and Metrunio links it to the order and its journey. That belongs where people look it up: in your privacy notice and in the description of analytics consent in your cookie banner. State the purpose (“how customers become aware of us”), that the answer is linked to the order, and how long it is kept, namely as long as the rest of your measurement data.

Legal note

The question only appears with consent to analytics. Whether that consent also covers the post-purchase question depends on what your banner says about analytics; you check that as the controller. A checkbox of its own is not automatically needed for this, nor is a new data processing agreement: the answer is a measurement event like a page view.

Shopify and Shopware

The widget works on any thank-you page where you can add code of your own. The Shopify app, the Shopware plugin and the WordPress plugin do not include it. On the Shopify thank-you page the question would need a checkout extension, in Shopware a block in the plugin.

Revisado por última vez el 15 oct 2026

En el portal del cliente

Go to settings

También se pregunta

  • How did you hear about us?
  • Survey after checkout
  • Can the post-purchase question use the formal address?
  • Set up a post-purchase survey
  • How do I see purchases from podcasts, radio or TV?
  • How do I see recommendations and word of mouth?
  • Ask customers where they came from
  • What does “self-reported” mean?
  • Is the post-purchase question available for Shopify or Shopware?
  • Is the post-purchase question anonymous?
  • Do I have to mention the post-purchase question in my privacy notice?

Artículos relacionados

  • What do “measured” and “attributed” mean?

    Why does Metrunio separate measured from attributed figures?

    Measured means directly observed: an impression, a viewable impression, a click, a conversion. Attributed means a share distributed by a model; the product keeps both layers apart and never blends them. Alongside them are values you decide yourself (“set”), answers from your customers (“self-reported”) and figures an ad platform reports about itself (“reported”); there is no “estimated” layer.

  • Why is a conversion not attributed?

    What does “unattributed” mean, and how do I improve coverage?

    “Unattributed” means the model found no touchpoint for this conversion that it considers. Either none falls inside the attribution window and is linked by a shared identifier, or there are only touchpoints of a kind the model does not distribute. Metrunio does not invent a contact in that case.

  • 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.

  • What does the tracking SDK offer?

    Which JavaScript calls are available?

    The SDK provides init, setConsent, page, track, identify, conversion, goal and reset, plus paymentReference for Stripe and PayPal, fillForm for forms, and renderSurvey and survey for the post-purchase question. It loads asynchronously, queues calls made before it loads, and sends events in batches.

  • How is a journey created?

    How do individual signals become one coherent journey?

    A journey is a chain of measured signals with timestamp, source and identifier, not a reconstruction. Signals are joined when they carry a shared, unambiguous identifier.

  • How long is data retained?

    Which retention periods apply and can I change them?

    Raw events are retained for 180 days by default, 90 days on the free Start plan; the period is configurable per tenant up to the plan’s limit and enforced automatically. Journeys, touchpoints and conversions share the period of the raw events they were derived from and are deleted with them, or earlier if a deletion is requested. If a change of plan lowers the limit below the configured period, we announce the reduction 30 days in advance.

Mira lo que cuentan tus datos.

Echa un vistazo primero a la demo. Por ahora, solo hay cuenta propia con invitación.

Abrir la demoSolicitar acceso