Skip to main content
TrackingConsultingFree audit
RegiondoTours, activities & attractions

Conversion tracking for tours and activities on Regiondo

Regiondo's booking widget is unusual: it looks for gtag or Google Tag Manager on your page and sends GA4 ecommerce events - view_item, add_to_cart, begin_checkout and purchase - straight into them, with no ID set in the widget itself. That makes tour bookings visible to GA4 out of the box. It also means the widget only reports as well as the page it sits on, and with a separate Google Ads conversion field and no confirmed Meta support, the same purchase can be counted twice in one place and missed in another.

Get my free conversion tracking auditSee what we check

Free30 minutesNo obligation

By Ariful IslamHow Regiondo works ↓

Regiondo · what breaks

Where Regiondo tour bookings get double counted or lost

  1. 01

    The widget is only as good as your page's tags

    If gtag or GTM loads late or is blocked, the purchase event has nowhere to go.

  2. 02

    Google Ads counting from two places

    The AW- field and an imported GA4 purchase can each record the same booking.

  3. 03

    Meta left out

    Regiondo's documented events go to Google's tags; Meta Pixel support is not confirmed.

  4. 04

    GTM only on higher plans

    On plans without it, tour operators lose the flexible route.

Regiondo · the fix

What changes — Regiondo

  • One purchase per booking everywhere

    Google Ads counting from a single source, deduplicated.

  • Meta and others built off the widget's own events

    Using GTM's custom-event trigger for widget purchases.

  • Server-side backstop

    Purchases sent through a first-party container so browser blocking does not erase them.

Regiondo · architecture

What Regiondo actually lets you do

From Regiondo's tracking documentation. Meta support is listed as a check.

  1. 1

    Automatic GA4 ecommerce events

    The widget detects gtag or GTM on your page and sends view_item, add_to_cart, begin_checkout and purchase.

  2. 2

    No ID needed inside the widget

    Measurement depends entirely on the tags already on your page.

  3. 3

    A GTM custom-event trigger for widget events

    The hook for sending the same purchase to other platforms.

  4. 4

    A Google Ads conversion ID (AW-) field

    Direct Google Ads conversions, which need to be reconciled with any GA4 import.

  5. 5

    Check Meta Pixel support and your plan's GTM access

    GTM is available on Grow and Pro plans; Meta Pixel handling is not confirmed, so we test it.

Regiondo · diagnose

Debugging the Regiondo widget, page first

Start with the page, not the widget.

  1. 01

    Book a test tour and watch the dataLayer

    If purchase never appears, the parent page's tags are the problem.

  2. 02

    Check Google Ads for two purchase actions

    The AW- field and a GA4 import both set as primary is the classic duplicate.

  3. 03

    Look for Meta purchases at all

    Most Regiondo sites have none, because nothing sends them.

  4. 04

    Confirm value and participant count

    Missing participants hide which campaigns sell group tours.

  5. 05

    Check consent behavior on the widget page

    A banner that delays tags can swallow fast checkouts.

Regiondo · prove

The QA evidence — Regiondo

On a live tour booking through the embedded widget.

Source of truth

Regiondo booking export - order number, product, date, participants and amount

  • A test booking showing view_item through purchase in the dataLayer, in order.
  • One Google Ads conversion per booking, from a single source.
  • Meta purchase received with the same order ID and value.
  • The server-side backup and the widget's browser event confirmed to merge into a single purchase.
  • A cancellation confirmed reversed.
  • Regiondo order numbers matched one to one against each platform for a finished month, and the match rerun four weeks later.

Regiondo · free audit

What we check in the free audit

  • Book a test tour and watch the dataLayer
  • Check Google Ads for two purchase actions
  • Look for Meta purchases at all
  • Confirm value and participant count
  • Check consent behavior on the widget page

Checked against

Regiondo booking export - order number, product, date, participants and amount

Get my free conversion tracking audit

Free30 minutesNo obligation

Regiondo · when not to buy

When Regiondo's native events are enough

The widget already feeds GA4, which covers more than most tour operators realize.

  • If you advertise only on Google and the widget's GA4 purchases match your bookings, choosing one Google Ads source may be the whole fix.
  • If you are on a plan without GTM and spend little on Meta, the native GA4 events are a reasonable place to stop.
  • If most bookings come through resellers or the phone rather than your widget, start with that channel instead.
  • Removing a duplicate Google Ads conversion is a quick job. We will tell you if that is all it is.

Regiondo · what we deliver

The event map for a Regiondo tour operator

  • view_item

    Tour or activity viewed in the widget.

  • add_to_cart

    Date, time and tickets chosen.

  • begin_checkout

    Checkout opened in the widget.

  • purchase

    The conversion, with booking value and participant count.

  • Ticket category

    Adult, child or group, carried on the purchase.

  • Booking cancelled or refunded

    Reversed against the original order.

Written guarantee

95%+ tracking accuracy

Measured against Regiondo booking export - order number, product, date, participants and amount. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Regiondo questions, answered

Usually two things: Google Ads counting the same purchase twice, and Meta receiving nothing. The widget's own events are a good base; they just need routing to one place per platform.

More on Regiondo

Free · 30 min

One Regiondo booking, one conversion, every platform

Book the free call WhatsApp

Free30 minutesNo obligation