
Easily track customer events across your store with our app's Google conversion pixel, and send accurate data to Google Ads from the moment it goes live. Product views, cart activity, checkout, and purchases are all recorded for you, with no theme edits and nothing to maintain as Google changes its requirements.
A conversion pixel that shows as installed is not the same as a pixel reporting every sale correctly. Google Ads bids, reports, and learns from whatever lands in the account, so a small reporting gap usually turns into a budget decision you never meant to make.
Google generally takes up to 24 hours to verify a new conversion pixel, and it needs at least one conversion before the status moves past unverified. Later, a theme edit or an account change can flip a working tag to tag inactive, and nothing in Shopify tells you it happened.
A conversion request reaching Google Ads and Google Ads recording a valid conversion are two separate stages. Without both timestamps, a sale that was sent correctly but failed validation looks identical to one that was never sent at all.
Enhanced conversions rely on consented first party details such as an email address. When those fields are incomplete, or Google is temporarily unable to process them, your account raises a warning and fewer buyers get matched back to the ads they clicked.
Every line item sent with a purchase needs an ID matching the Content ID in your Google Merchant Center feed. When the two formats differ, product level reporting breaks quietly, with no error anywhere pointing at the cause.
Nabu for Google Ads Pixel brings each of these into one screen inside your Shopify admin.
A conversion pixel is a small piece of tracking code that records what shoppers do on your store, such as viewing a product, searching, adding an item to the cart, starting checkout, or buying. Each action is sent to Google Ads as an event carrying a conversion ID, a conversion label, and the order value, and Google uses those events to credit campaigns, feed smart bidding, and build remarketing lists.
That was enough while every event could be tied back to the person who clicked the ad. Consent choices, signed in matching, and journeys that start on a phone and finish on a laptop have changed it, so Google now leans on hashed customer data to close the gap. Both layers report against the same conversion action.
Conversion pixel: Fires when the event happens and reports what was bought and for how much. This is the layer that tells Google a conversion took place at all.
Enhanced conversions: Sends consented first party details alongside that event, hashed before they leave your store. An email address works best, a name with a full home address also works, and a phone number counts only when it comes with one of the other two.
In Nabu for Google Ads Pixel, enhanced conversions are switched on by default when you create a Purchase or Add to Cart pixel, and you can turn them on or off for each pixel from its detail page afterwards.
Shopify’s Google & YouTube channel measures purchase, cart, and checkout events. It also supports enhanced conversions and configurable destinations. Nabu adds dedicated pixel management, post-purchase tracking, and analytics.
Google & YouTube already offers strong conversion tracking. Nabu adds dedicated pixel workflows, post-purchase support, and in-app analytics for merchants who need additional control.
No developer and no theme code. Here is the whole setup:
Click Sign in with Google and accept the permissions the app asks for, so it can create pixels and send conversions to your Google Ads account. If you skip this during onboarding, you can connect later from Settings, then Account Settings, then Account.
Click Setup app embed block, choose your current theme, and switch on the AdNabu app under App Embeds in the theme editor. Click Save, and the app can start tracking on your store.
Choose the events you want Google Ads to receive, such as Purchase, Page View, Add to Cart, and Initiate Checkout. You can switch individual events on or off later as your campaigns change.
Prefer to set things up yourself? The app also gives you the option to create a pixel manually.
Selling an upsell after checkout? Open Settings, then App configuration, then Post Purchase, enable it, and paste the generated script into the post purchase page field of your checkout settings so that order value is reported too.
Bottom line: Every step happens inside Shopify and the app, so there is no snippet to paste again when Google updates its tracking requirements.
Every store benefits from clean conversion data, though a few situations make the difference impossible to ignore.
Target ROAS and Maximize Conversion Value learn from the conversions you report back. The more budget running through those strategies, the further a handful of unreported purchases can pull bidding away from what actually sells.
Orders added after checkout through apps such as OCU or ReConvert sit outside the standard purchase event. One script in your checkout settings brings that revenue into the same conversion report as the original order.
Client accounts, brand accounts, and MCC structures are all handled from a single Shopify admin, so checking whether a pixel is still firing no longer means signing in and out of Google Ads.
Snippets placed by hand tend to linger in checkout settings and theme files long after anyone remembers adding them. Duplicates are picked up during setup, so two tags do not end up reporting the same sale twice.
Page views, product searches, add to cart, and begin checkout can each be switched on for a given pixel, which gives Google the earlier signals it uses for audience building and broader campaign types.
Each shopper's consent choice is passed to Google Ads in line with your store's customer privacy settings, and it works with Shopify's own cookie banner as well as third party banner apps.




