Google Analytics 4 (Measurement Protocol)

SignalRelay Pro delivers your conversions to Google Analytics 4 (GA4) from your own server, using the official Measurement Protocol. Ad blockers never see the request.

Google Analytics 4 Setup

In your GA4 property, navigate to Admin → Data Streams.
Select your Web stream and copy the Measurement ID (begins with G-).
Scroll down and click Measurement Protocol API secrets.
Create a new secret and copy the generated secret string.
In WordPress, go to Settings → SignalRelay, open the Connections tab and, on the Google card, enter the Measurement ID and API secret. SignalRelay refuses to save an ID that is not G- followed by letters and digits.

What SignalRelay sends

Every event is translated to its native GA4 name (Lead → generate_lead, PageView → page_view, CompleteRegistration → sign_up, and so on) and delivered with its custom data (such as value and currency), the page location, and an anonymous first-party visitor ID.

No personal data reaches Google through this connection. SignalRelay does not send hashed emails, phone numbers or names to the Measurement Protocol, and it does not send the gclid. The destination is your GA4 property: Google Ads Enhanced Conversions is not a SignalRelay destination today.

Delivery is server-side only. SignalRelay does not install the Google tag (gtag.js) on your pages, so if you also run gtag or another GA plugin, both will report — decide which source you want as your GA4 truth for these events.

Test mode

GA4 has no test event code, and anything sent to the Measurement Protocol lands in your property permanently. Turn on Test mode on the Google card and events go to Google’s validation endpoint instead: the payload is checked, it is tagged for DebugView so you can watch it arrive, and nothing reaches your reports. Turn it off when you are done. While Test mode is off, Send test event asks you to confirm first, because the event would land in your property for good.