Connect Shopify to GA4 in One Click — Converlay Eliminates the Manual API Secret Setup

If you have ever tried to set up server-side GA4 tracking manually, you have probably hit the same wall: the Measurement Protocol API secret. Google Analytics 4 requires one to accept server-side events, but finding where to create it takes several menus deep inside the GA4 Admin interface. Many merchants generate the wrong kind of credential, enter it incorrectly, or abandon setup entirely. The result is that they never get the complete purchase data they came for.

With Converlay v2.17.0, that friction is gone. A new "Connect with Google" flow authenticates with your Google account via OAuth, lets you pick the exact GA4 property and data stream for your Shopify store, and auto-creates a Measurement Protocol API secret server-side — all without you ever opening GA4 Admin. Then v2.18.0, released the next day, removes the one remaining manual step: enabling the destination after provisioning now happens automatically too.

The result is that a Shopify merchant who has never touched the GA4 API can go from zero to full server-side event forwarding in the time it takes to authorize a Google OAuth prompt.

Why the Old Setup Process Was a Problem

GA4's Measurement Protocol is powerful — it lets any server send events directly to Google Analytics, bypassing browsers, ad blockers, and cookie restrictions entirely. But to use it, you need two pieces of information: your Measurement ID (which you can find on the GA4 data stream overview page) and a Measurement Protocol API secret (which is generated separately, in a different part of the same page, under a section many merchants never discover).

The path to that secret requires navigating to GA4 Admin, selecting your property, opening Data Streams, choosing your web stream, scrolling past several unrelated settings, and finally clicking "Measurement Protocol API secrets" in a subsection at the bottom. From there you create a new secret, give it a nickname, and copy the resulting token — which you then have to paste into Converlay's destination settings without making a typo.

Each of those steps is a potential failure point. Merchants sometimes create Firebase App secrets instead of web stream secrets. Others create the right kind of secret but on the wrong property, because they have multiple GA4 properties and picked the development one by accident. Even merchants who get everything right occasionally fat-finger the paste and spend an hour troubleshooting an API secret that is off by one character.

None of this is Google's fault — the Measurement Protocol is a developer API that was not designed for non-technical users. But Shopify merchants setting up analytics should not need to understand the internals of GA4's credential system just to get accurate purchase data.

How the New "Connect with Google" Flow Works

Starting with v2.17.0, the GA4 destination in Converlay shows a "Connect with Google" button instead of a manual credential form. Clicking it starts a standard OAuth authorization flow — the same login-and-consent process you see when any app requests access to your Google account.

Once you authorize, Converlay fetches your Google Analytics account, lists all the GA4 properties you have access to, and presents them in a property picker inside the Converlay dashboard. You select the property that belongs to your Shopify store — if you have multiple properties, the picker shows each one's name so you can identify the right one — and then pick the data stream within that property.

Converlay then calls the GA4 Management API server-side to create a Measurement Protocol API secret for that stream, stores the credentials securely against your shop, and the connection is established. You never see the raw API secret value, and you never have to copy-paste anything between tabs.

With v2.18.0, the destination is also enabled automatically after provisioning. Previously there was a final review-and-enable step where you had to toggle the destination on and save. That step still exists for merchants who want to review settings before going live, but for merchants who went through the OAuth picker flow — where selecting a data stream is already a clear expression of intent — Converlay now enables the destination and merges it with the stored credentials in a single server-side call. The toggle remains available at any time for pausing the destination.

What Gets Sent to GA4

The underlying event pipeline is unchanged — only the setup experience is different. Once connected, Converlay forwards your Shopify storefront events to GA4 using the Measurement Protocol, including:

• purchase — fired when an order is placed, with the full transaction ID, revenue, tax, shipping, currency, and item array. This is the most critical event for accurate e-commerce reporting.
• add_to_cart and remove_from_cart — triggered by Shopify storefront cart interactions, with item details.
• begin_checkout — fired when a customer starts the checkout process.
• page_view — sent for each page load, with canonical URL and referrer.
• view_item and view_item_list — product and collection views with full item metadata.

All events carry the GA4 client ID captured by the browser during the session. This means server-side events stitch correctly with browser-side sessions in GA4's user explorer and attribution reports — purchases appear under the correct session, not as isolated orphan events.

Event deduplication uses the transaction ID on purchase events, so if you also have browser-side GA4 tracking enabled, GA4 automatically prevents double-counting purchases using the same transaction ID. The server-side event fills in any gaps from ad blockers or browser script failures.

What You See in GA4 After Connecting

Within a few minutes of connecting, you should see server-side events appearing in GA4's Real-Time report. The purchase events come through with complete item arrays, so GA4's built-in e-commerce reports — Revenue, Transactions, Items Purchased — populate with real data.

The most visible improvement for most merchants is purchase event completeness. Browser-based GA4 tracking typically captures 60 to 80 percent of transactions — the rest are lost to ad blockers, browser privacy features, or customers who close the tab immediately after payment. Server-side tracking from Converlay captures purchases directly from Shopify's order webhook, so completion rates are consistently above 95 percent regardless of the buyer's browser or privacy settings.

If you run any Google Ads campaigns, that completeness matters for automated bidding. Google's Smart Bidding and Performance Max campaigns optimize toward conversion signals. When a significant fraction of purchases never reach GA4, the bidding algorithm under-values your true conversion rate and allocates budget conservatively. More complete purchase data means the algorithm has a more accurate picture of what actually converts, which typically translates to better campaign performance over time.

Session Token Reliability (v2.18.0)

One of the other fixes in v2.18.0 addresses a reliability edge case that could cause the occasional failed save. Converlay uses App Bridge session tokens for authenticated requests from the Shopify admin embed. Those tokens have a 60-second expiry, and under the old behavior, if a token expired in the small window between when it was issued and when the request was verified server-side, the save would fail with a 401 error.

v2.18.0 adds 10 seconds of clock-skew tolerance on the server-side token verification, and the client now automatically re-mints a fresh App Bridge token and retries once on a 401 response. For merchants with slower connections or any network latency, this eliminates a frustrating class of "please try again" errors that had nothing to do with their configuration.

Better Error Visibility When Google Blocks a Request

The v2.18.0 release also improves how GA4 API errors are surfaced. Axios, the HTTP client Converlay uses, wraps the raw response body in its own error message — which means that when Google returns a structured error (like a 403 with a reason field explaining which permission was missing), that context was previously swallowed. Merchants only saw "Request failed with status code 403."

Now, when Google returns a structured error response, Converlay extracts the reason and includes it in both the server logs and the merchant-visible error copy. If your Google account does not have edit access to the GA4 property you selected, you see a message explaining that rather than a generic failure. This makes troubleshooting much faster, especially in cases where the OAuth connection succeeded but the associated Google account lacks the right permissions on the property.

How to Connect Your Shopify Store to GA4

If you are already a Converlay user, the new flow is available in your Destinations settings today. Navigate to the GA4 destination and click "Connect with Google." If you had previously entered credentials manually, you can switch to the OAuth path at any time — the picker flow will update the stored credentials without affecting your event history.

If you are not yet using Converlay, setup takes a few minutes:

1. Install Converlay from the Shopify App Store and open it in your Shopify admin.
2. Go to Destinations and select Google Analytics 4.
3. Click "Connect with Google" and authorize with the Google account that has access to your GA4 property.
4. Pick your GA4 property and data stream from the dropdown.
5. Converlay creates the API secret and enables tracking automatically.

Within minutes, GA4 will start receiving server-side purchase events from your Shopify store. Your conversion data will be more complete, your attribution will be more accurate, and your Google Ads campaigns will have better signals to work with.

Accurate GA4 Data Without the Setup Headache

Server-side GA4 tracking has always been the right approach for Shopify stores. The limitation was never technical — the Measurement Protocol is reliable and well-supported. The limitation was setup friction: a buried credential, a multi-step manual process, and too many places to make a mistake.

The "Connect with Google" OAuth flow and auto-enable changes in v2.17.0 and v2.18.0 eliminate that friction. Authorizing a Google account and selecting a property takes less than a minute, and Converlay handles the API credential lifecycle from there.

If you want complete, accurate e-commerce data in GA4 without the credential-hunting, the new setup flow is available in Converlay today. Install Converlay from the Shopify App Store and connect your GA4 property in a single OAuth step.