Google Ads, Merchant Center, GA4 & Search Console
Google Shopping, Google Ads, Google Analytics 4 and Google Search Console, built as four first-party Web Shop Manager 6.0 applications on one platform. Your Shopping listings carry the year, make and model the part fits. Your conversions are uploaded from the order rather than guessed at in a browser. Your feed, your ads and your analytics all identify the part by the same SKU.
Visit Google
Learn more about Google, or see it integrated on your Web Shop Manager store.
-
Website
www.google.com
Get in touch with us
Reach out to us for any inquiries or support, and let’s connect!
Four Google integrations, built by us, and every one of them knows what the part fits.
Google Shopping, Google Ads, Google Analytics 4 and Google Search Console are four different systems with four different APIs, and on most platforms they arrive as four different bolt-ons: a feed exporter, a tag container, a plugin, a spreadsheet. Web Shop Manager 6.0 ships all four as first-party applications on one platform, sharing one OAuth grant, one product key and one fitment convention. Your Shopping listings carry the year, make and model the part fits. Your conversions are uploaded from the order rather than guessed at in a browser. Your GA4 revenue and your Merchant Center feed join on the same SKU.
Built in July 2026 as four applications on the Web Shop Manager 6.0 application platform, against current Google APIs: Merchant API v1, Google Ads API v24, the GA4 Measurement Protocol and the Search Console API. 857 automated tests across the four. Offline conversion upload has been run against a live Google Ads account on Web Shop Manager’s own developer token. Same build standard as our Meta, Klaviyo and Shopper Approved integrations: one platform, one outbox discipline, one test bar.
See the four applications · See fitment in the feed · See the comparison · Read the FAQ
The four applications, and what each one actually does
These are not settings screens that hand you a tracking id and wish you luck. Each one is a Web Shop Manager 6.0 application that talks to Google’s API on your behalf, on your store’s own events, with its own retry queue and its own tests.
Google Merchant Center
Merchant API v1
Your catalog, in Google Shopping and free listings, with vehicle fitment attached to the listing itself.
- Every product and variant is pushed when it is created, changed, deleted, or goes in or out of stock. Not a nightly file, not a spreadsheet, and not a link to a feed URL Google may or may not fetch today.
- Vehicle fitment is written into the listing four separate ways: campaign labels, a structured Vehicle Fitment section, a title suffix and a Fits line in the description.
- itemGroupId is set on every variant, so your sizes and finishes are grouped as one product in Shopping rather than bidding against each other.
- A GTIN is check-digit validated before it is sent. A part with no barcode goes out with its MPN taken from your SKU, and a part that genuinely has neither declares that instead of failing review.
- A refresh pass re-sends your products before Google’s 30 day expiry window, so listings do not quietly disappear because nothing touched them.
Google Ads
Google Ads API v24
Purchases uploaded from the order, refunds corrected after the fact, and audiences kept current without an export.
- An order that is paid uploads as an offline click conversion with its real value and currency. Not a pixel that had to survive a shopper closing the tab.
- A refund or cancellation uploads a conversion adjustment: a retraction when the whole order goes back, and a restatement down to the amount you actually kept when part of it does. Your reported ROAS stops counting revenue you refunded.
- Email and phone are hashed with SHA-256 to Google’s own normalization rules before anything leaves your server.
- Two Customer Match audiences are maintained for you: people who bought, and carts abandoned past a threshold you set.
- It creates the purchase conversion action for you, and it queries your account for an existing purchase action first, so you are warned about double counting instead of discovering it in a report.
Google Analytics 4
GA4 Measurement Protocol
The money end of the funnel, sent from the server. No Tag Manager container required for any of it.
- begin_checkout, add_shipping_info, add_payment_info, purchase and refund are all sent by your store, from your store’s own checkout and order events.
- purchase does not depend on a browser reaching a thank-you page. A shopper on one bar of signal next to the truck they are fixing still gets counted.
- A refund or cancellation sends a refund event computed as a delta, so a partial refund reports the partial and not the whole order.
- item_id uses the same SKU-first key as the Merchant Center feed. Merchant Center, Ads and GA4 all identify the part the same way, which is the difference between three reports and one answer.
Google Search Console
Search Console API v3, URL Inspection v1
Property setup, sitemap submission, search performance and index checks, inside your store admin.
- Verify the property from the admin: a meta tag for a URL prefix property, a DNS TXT record for a domain property. No file to upload and nothing to paste into a template.
- Submit and manage your sitemap from the same screen that built it.
- 28 days of clicks, impressions, click-through rate and average position, compared against the prior 28 days, plus your top ten queries and your top ten pages.
- Run URL Inspection against your money pages: is it indexed, is the canonical the one you chose, when did Google last crawl it.
- It reads. It holds no permission on your store data at all, and it never touches an order or a customer record.
Fitment is not a filter on your website. It belongs in the listing.
Year, make and model decide whether a part is relevant at all, and a Shopping listing that does not carry them is competing on price against parts that do not even fit. Fitment is not one of Google’s standard product attributes, so the question is what a platform does with it anyway. Web Shop Manager reads the fitment on your product and writes it into four places Google actually uses: the custom labels you segment campaigns with, a structured detail section a shopper reads, the title, and the description.
POST /products/v1/accounts/{account}/productInputs:insert
"title": "Heavy Duty Tie Rod End for 2004-2011 Ford F-150",
"itemGroupId": "your-product-id",
"customLabel0": "Ford", <- dominant make
"customLabel1": "F-150", <- dominant model
"customLabel2": "2004-2011", <- year range
"customLabel3": "multi-fit", <- or single-fit
"productDetails": [
{ "sectionName": "Vehicle Fitment",
"attributeName": "Ford F-150 XLT",
"attributeValue": "2004-2011" } ],
"description": "... Fits: 2004-2011 Ford F-150 XLT; ..."
Your Google stack assembled from parts, and your Google stack built into the platform
The right-hand column is the ordinary way this gets done on a general-purpose ecommerce platform: a feed app or a scheduled file for Shopping, a Tag Manager container and a gtag snippet for Ads and Analytics, and Search Console in a separate browser tab. It is a route that works, plenty of stores run it, and none of this is a criticism of any particular tool. The point of the table is what changes when the platform itself holds the Google connection, and every claim on the right is about what that assembled route requires by construction, not about any vendor’s implementation.
| What you actually get | Web Shop Manager 6.0 | A feed app plus a tag container |
|---|---|---|
| What Google learns about the part | ||
| Vehicle fitment on the Shopping listing | ●custom labels, a structured Vehicle Fitment section, the title and the description | ○fitment is not a standard Google product attribute, and a catalog export has no vehicle data to map |
| Campaign segmentation by make, model and year range | ●customLabel0 through customLabel3 are filled from fitment automatically | ◙custom labels exist, but something has to decide what goes in them |
| Variants grouped rather than competing | ●itemGroupId set on every variant, always | ◙supported by Google, and a field somebody has to map correctly |
| A part with no barcode submitted correctly | ●validated GTIN, MPN from SKU, or an honest declaration that there is neither | ◙depends entirely on how the export is configured |
| Listings refreshed before Google’s 30 day expiry | ●a scheduled refresh pass, plus a push on every catalog change | ◙as often as the feed is fetched, which is not the same as when the product changed |
| What Google learns about the sale | ||
| Purchase measured from the order, not the browser | ●offline click conversion upload for Ads, Measurement Protocol for GA4 | ○a tag on a confirmation page has to load and fire to be counted |
| A refund reduces reported revenue | ●conversion adjustment to Ads, refund event to GA4 | ◙possible, and a separate integration nobody builds on day one |
| A partial refund reported as partial | ●restated to the amount you actually kept | ○not a thing a tag can do after the fact |
| Feed, ads and analytics joined on one product key | ●one SKU-first key shared by Merchant Center, Ads and GA4 | ○three tools, three id schemes, and a reconciliation problem |
| What it costs you to run | ||
| Nothing pasted into a template to measure a sale | ●connect the account, choose the settings, done | ○a container, a snippet and a tag per event, by definition |
| One Google sign-in across all four surfaces | ●a single OAuth grant extends across the four applications | ○each tool authorizes separately |
| A failed send lands where a human sees it | ●retried on a widening backoff, then parked in a needs attention queue | ○not documented, and usually not visible until a number looks wrong |
| Search Console inside the admin you already use | ●verification, sitemaps, 28 day performance and URL inspection | ○a separate tool in a separate tab |
● Built into the Web Shop Manager 6.0 applications ◙ Available, with configuration or a manual mapping step ○ Not available, or not a property of that route
- 1. The right-hand column describes the assembled route in general terms: a catalog feed for Shopping plus browser tags for Ads and Analytics. No specific product is named or measured, individual tools differ, and several of them are good. Where a capability exists in that route but requires someone to configure or map it, we have marked it available with a manual step rather than unavailable.
- 2. Fitment: year, make and model are not standard Google Merchant Center product attributes. Web Shop Manager places them in attributes Google does support, which is why they arrive as custom labels, a structured product detail section, a title suffix and a description line rather than as a fitment field.
- 3. Product expiry: Google expires a Merchant Center product that has not been refreshed for 30 days. Web Shop Manager pushes on every catalog change and additionally re-sends on a schedule inside that window.
- 4. Google Ads: purchases are uploaded as offline click conversions and corrected with conversion adjustments. Web Shop Manager also surfaces the Google site tag for your account in the admin, because a click identifier collected in the browser improves match quality on top of the identifier matching the upload already does. Conversion upload has been exercised against a live Google Ads account on Web Shop Manager’s developer token. Customer Match audience uploads additionally depend on the entitlements Google grants your account.
- 5. Google Analytics 4: the purchase event is sent server side, and for that to be correct the storefront tag must not also send purchase. This is a requirement of the integration rather than a preference, because a duplicated purchase is worse than a late one. The other events described here are likewise sent from the server.
- 6. Search Console: the integration reads search performance and index status and writes only property verification and sitemap submissions. It requests no permission on store data. Search Console reports a two day data lag, which is Google’s, not ours.
- 7. Capabilities described are those of the Web Shop Manager 6.0 applications as built and covered by their automated test suites. Google requires its own approval and verification steps for some of these APIs, including Merchant Center service provider access, and availability on your account depends on those being in place.
Score your current setup against this table, book 20 minutes
One product key, one Google grant, one place to look when a number is wrong.
The reason these four are worth building together is that Google treats them as one business and most stores cannot. Your Shopping listing, your conversion upload and your GA4 item all have to be talking about the same part before any report is worth reading, and on Web Shop Manager 6.0 they are: the same SKU-first key identifies the product in the Merchant Center feed, in the conversion you upload to Ads, and in the GA4 item. One Google sign-in covers all four applications. When something does fail, it fails somewhere you can see, with a retry behind it, rather than becoming a gap in a chart three weeks later.
Web Shop Manager is a fitment-native platform built for aftermarket parts and powersports, where the vehicle decides everything. The same fitment convention these Google applications read is the one our Meta and Klaviyo integrations read, so the vehicle data you maintain once reaches Shopping, paid social and your email program without being re-entered anywhere. It pairs with our Marketing and SEO services and the accuracy you get from product data tools. If you would rather have specialists run the campaigns themselves, our partner Logical Position manages Google Ads for Web Shop Manager stores.
See the rest of our platform integrations, or the wider picture in automotive eCommerce.
Google and Web Shop Manager: what parts sellers ask
Straight answers for aftermarket, auto parts and powersports retailers running Shopping and Ads today, or about to.
Do I still need Google Tag Manager?
Not for any of the measurement described here. The GA4 ecommerce events and the Google Ads conversions are sent by your store to Google’s APIs, from the order and checkout events your store already fires, so there is no container to build and no tag to maintain for them. There is one thing worth being precise about: for Google Ads, the admin also shows you the Google site tag for your account, because a click identifier captured in the browser improves how well Google can match an uploaded conversion back to the ad that earned it. That is additive. The conversion is uploaded either way. And if you already run a Tag Manager container for something else, keep it, with one condition: the storefront must not also send a GA4 purchase event, because two purchase events for one order is worse than one arriving from the server.
How does vehicle fitment get into a Google Shopping listing?
Google has no fitment attribute, so Web Shop Manager writes fitment into the attributes Google does have. Your product’s year, make and model data becomes four things at once: the four custom labels you segment campaigns with, filled with the dominant make, the dominant model, the year range and whether the part is single-fit or multi-fit; a structured Vehicle Fitment detail section a shopper can read on the listing; a suffix on the title along the lines of for 2004-2011 Ford F-150; and a Fits line in the description. Year ranges are collapsed rather than listed one year at a time, and a universal part that fits hundreds of vehicles is summarized per make instead of producing a listing nobody can read.
Why upload conversions from the server instead of using a pixel?
Because the order is the truth and the browser is a rumour. A tag on a confirmation page has to survive ad blockers, tracking prevention, a shopper who closes the tab the second the payment clears, and the one bar of signal they have while standing next to the vehicle they are working on. An offline conversion upload happens after the order is paid, with the real order value, from your server. It is also the only route that can correct itself: when a customer refunds, Web Shop Manager uploads a conversion adjustment that retracts the conversion outright, or restates it down to the amount you actually kept on a partial refund. A pixel cannot go back and change its mind, which is why so many stores are optimising campaigns against revenue they gave back.
What happens to my Merchant Center account and my existing campaigns?
Nothing is migrated and nothing is rebuilt. You connect the Google account you already use, and the integration works with the Merchant Center account and the Ads account you already have, with the campaign structure and history already in them. For Google Ads it goes one step further and looks before it writes: it queries your account for an existing purchase conversion action, so if you already have one firing you are told about the double counting risk rather than finding it in a report next month.
Does the Search Console integration have access to my orders or customers?
No, and that is deliberate. The Search Console application requests no permission on your store data at all. It cannot read an order, a customer or a product, because it does not need to: everything it shows comes back from Google. It verifies your property, submits your sitemap, pulls 28 days of clicks, impressions, click-through rate and average position against the prior 28 days with your top ten queries and pages, and runs URL Inspection against the pages you nominate so you can see whether Google has actually indexed them and which canonical it chose. The two day lag on that data is Google’s own.
What happens when a send to Google fails?
It is retried, and if it keeps failing a human finds out. Every outbound message goes through a guarded outbox rather than straight out of the web request, so a Google API that is briefly unavailable, rate limiting you, or returning an expired token does not silently drop a conversion or a product update. Failures are retried on a widening backoff, and one that keeps failing stops retrying into the void and parks where somebody can see it. That is the difference between a problem you get to fix and a chart with a gap in it that nobody can explain three weeks later.
Do I have to connect all four, or can I start with one?
Start with whichever one is costing you money today, and they are genuinely independent applications. Most parts sellers start with Merchant Center, because getting fitment onto Shopping listings changes which searches a part can even appear for, and then add Ads so the spend against those listings is measured from real orders. GA4 and Search Console are the two that answer the follow-up questions. There is one shared benefit to running them together rather than separately: one Google sign-in covers all four, and the same product key identifies the part in the feed, in the conversion and in the analytics, so the numbers reconcile instead of arguing.
Is this included with Web Shop Manager 6.0?
These are first-party Web Shop Manager applications rather than third-party subscriptions with their own bills and their own support queues. Your Google API access is your own, under your own Google account, and Google requires its own approval steps for some of these surfaces, including service provider access for Merchant Center. Which applications are enabled on your store is a conversation worth having on a call with your catalog in front of us, because the honest answer depends on what you are already running.
Bring your catalog. We will show you your own parts in a fitment-labelled Google feed.
Book 20 minutes. Bring the parts you cannot get to show up in Shopping, and the campaign whose numbers you do not believe. We will walk through what Google actually receives about them today, and what it receives on Web Shop Manager 6.0.
Get Started Now: Put Fitment In Front Of Google
Bring your catalog and the campaign whose numbers you do not believe. We will walk through what Google receives about your parts today, and what it receives on Web Shop Manager 6.0.
See Google Integrated On Your Store
Ready To Grow Your Business?
Ready to grow your aftermarket eCommerce presence and lift conversions across auto, truck, powersports, marine, and more? Connect with
Web Shop Manager for tailored solutions: strategy, platform, and performance in one team.