Tracking doo Registrations with Analytics Tools

Analytics tools such as Google Analytics, GA4, or other tracking solutions help you measure and understand the performance of your website: page views, traffic sources, clicks, interactions, and much more.

But how can you determine how many visitors actually register for an event when the doo registration form is embedded via a widget?

The good news:
✅ doo provides all relevant e‑commerce and interaction data
✅ The implementation and processing of this data is entirely up to you

1. Basic principle: Manual integration required

If you embed a doo registration form on your website via a widget (iframe), user interactions are not tracked automatically in your analytics tool.

Instead, the following applies:

• doo sends tracking events via postMessage to the parent window
• These events must be actively received on your website
• and then forwarded to your analytics tool

2. Requirements & responsibilities

What doo provides

• Technically correctly formatted dataLayer / e‑commerce events
• Transmission of events from the doo widget to the parent window
• Consistent event names and parameters (e.g. View, Add to Cart, Purchase)

What you need to implement

• ✅ An event listener on your website
  (e.g. via script or GTM Custom HTML tag)
• ✅ An analytics tool of your choice (e.g. GA4, Adobe, Matomo)
• ✅ Configuration of:
  • GTM tags
  • triggers
  • variables
  • event mappings

💡 doo is not tied to any specific analytics tool.

3. Receiving doo events on your website

In order to further process the events sent by doo, they must first be captured in the parent window and written to your website’s dataLayer.

3.1 Custom HTML tag in Google Tag Manager

Create a Custom HTML tag in your GTM container that:

• fires on all pages where the doo widget is embedded
• listens for message events
• pushes valid doo events into the dataLayer

Example: Event listener script

<script>

(function () {

  var allowedOrigin = 'https://doo.net';

  window.addEventListener('message', function (event) {

    if (event.origin !== allowedOrigin) return;

    if (!event.data || !event.data.event) return;

    window.dataLayer = window.dataLayer || [];

    window.dataLayer.push(event.data);

  });

})();

</script>

📌 This script only ensures that doo events are available in your website’s dataLayer.
No data is sent to an analytics tool at this stage.

4. Connecting your analytics tool (e.g. GA4)

Once the doo events are available in the dataLayer, you can forward them to your analytics tool:

1. In Google Tag Manager, create:
   • GA4 event tags (or tags for your chosen analytics system)
   • appropriate variables (e.g. event, ecommerce.*)
2. Map the doo event data to your analytics schema
3. Decide yourself:
   • which events are relevant
   • which should count as conversions
   • which parameters should be passed

doo does not impose any technical requirements here.

5. Trigger configuration

Appropriate triggers must be created for tracking.

Typical setup:

• Trigger type: Custom Event
• Event name examples:
  • iframe.purchase
  • iframe.add_to_cart
  • iframe.begin_checkout

👉 All doo events are clearly identifiable (e.g. via an iframe. prefix or clearly defined event names).

This ensures that only events coming from the doo widget are processed.

6. Using doo data in your analytics tool

After a successful setup:

• doo events will appear in your analytics tool
• you can use them for:
  • conversion tracking
  • funnel analysis
  • revenue reports
  • campaign optimization

All analysis is performed according to your own requirements within your analytics system.

7. Summary

✅ doo provides standardized tracking events
✅ You receive these events via an event listener
✅ The choice and configuration of the analytics tool is up to you
✅ Maximum flexibility with no tool lock-in

If you have questions about the event structure or example events, our doo team will be happy to help.
However, the actual analytics implementation is always handled on your side.