Noterro's patient portal fires a Google Analytics 4 event called booking_complete every time a patient successfully books an appointment online. Once you connect that event to Google Ads, you can see which campaigns, keywords, and ads are actually producing bookings — not just clicks. This feature requires the Noterro Max plan.

Connect Booking Data to Google Ads

This article walks through the full setup. It takes about 15 minutes, and most of the work occurs in Google Analytics and Google Ads rather than in Noterro.

Prerequisite: Use the Same GA4 Property as Your Website

Your Noterro patient portal lives on its own subdomain — yourclinic.noterro.com — while your marketing site lives on your own domain, for example yourclinic.com.

For attribution to work, both must report into the same GA4 property. The measurement ID you enter in Noterro has to be the same G-XXXXXXXXXX you already use on your website.

To check which property your website uses: in Google Analytics, go to Admin → Data Streams, open your web stream, and copy the Measurement ID at the top right. It starts with G-.

Step 1 — Enter Your GA4 Measurement ID in Noterro

1. In Noterro, go to Clinic Settings → Patient Portal Settings.
2. Open the Web Address & Online Booking tab.
3. Find the Google Analytics section.
4. Paste your measurement ID into the GA4 ID field (format: G-XXXXXXXXXX).
5. The field saves automatically. Noterro will now load Google Analytics on your patient portal and fire the booking_complete event on every completed booking.

Step 2 — Configure Cross-Domain Measurement

This process allows a visitor who clicks your ad, lands on your website, and then jumps to your booking portal to be treated as one continuous session.

1. In Google Analytics, go to Admin → Data Streams and click your web stream.
2. Click Configure tag settings.
3. Click Configure your domains.
4. Add both domains:
   • yourclinic.com — your website
   • yourclinic.noterro.com — your Noterro patient portal
5. Save.

Without this step, the move from your website to the booking portal looks to Google like the visitor left, and a brand-new person arrived. The booking gets credited to "Referral: yourclinic.com" instead of to your ad campaign.

Step 3 — Mark Booking_Complete as a Key Event

Google Ads can only import GA4 events that are marked as key events (formerly called "conversions").

1. Take one test booking on your portal so the event is registered. Events must be seen at least once before they appear in this list — it can take up to 24 hours.
2. In Google Analytics, go to Admin → Events.
3. Find booking_complete in the list.
4. Toggle Mark as key event on.

Step 4 — Link Google Analytics to Google Ads

1. In Google Analytics, go to Admin → Product links → Google Ads links.
2. Click Link, choose your Google Ads account, and follow the prompts.
3. Leave Enable personalized advertising and Enable auto-tagging at their defaults unless you have a specific reason to change them.

You need admin access on both the GA4 property and the Google Ads account to complete the link.

Step 5 — Import the Conversion into Google Ads

1. In Google Ads, go to Goals → Conversions → Summary.
2. Click New conversion action.
3. Choose Import.
4. Select Google Analytics 4 properties → Web.
5. Tick booking_complete and click Import and continue.

Then open the new conversion action and set:

• Goal category — Submit lead form or Book appointment, whichever your account offers.
• Value — set to Don't use a value, or enter a fixed estimated value per booking. Noterro does not send an appointment value.
• Count — One is usually correct for clinics, so a patient booking three visits in one session counts as one conversion. Choose Every if you want each booking counted separately.
• Include in "Conversions" — turn this on if you want the conversion to influence Smart Bidding.

Step 6 — Confirm Auto-Tagging is Enabled

1. In Google Ads, go to Admin → Account settings.
2. Confirm Auto-tagging is on.

Auto-tagging appends a gclid parameter to the landing page URL when someone clicks your ad. Google Analytics stores that ID for the session, cross-domain measurement carries the session onto the booking portal, and the imported key event attributes the booking back to the campaign. Every step in this article depends on that chain.