A measurable client benefit
Give e-commerce clients access to the Google CSS model and potential CPC savings in Shopping campaigns.
A ready-to-sell White Label CSS model for agencies
Preview how your CSS brand can appear next to products in Google Shopping
A ready-made agency product
Feedve White Label CSS is a price-comparison service and product aggregator launched under your own brand. You sell the service. We provide the infrastructure, onboarding and operational support.
Give e-commerce clients access to the Google CSS model and potential CPC savings in Shopping campaigns.
Your agency name can appear next to product ads. The service strengthens your own offer and client relationship.
Set your own resale price and margin. One flat Feedve subscription supports an unlimited number of clients.
Use the existing Feedve CSS infrastructure instead of creating and maintaining your own comparison platform.
The Merchant Center switch is administrative. Existing campaign history and optimisation data are preserved.
We support onboarding, Merchant Center migration and the technical side of the service.
What you receive
Launch the service with your branding and add client stores without paying for every new account.
The economics improve with every store you add. You are not charged per click, per product or per client account.
How it works
The process is structured so your team can focus on clients, not infrastructure.
Purchase the monthly or annual White Label CSS plan securely through Stripe.
Provide the CSS name, domain option, company details and visual assets.
Feedve prepares the branded CSS environment and completes the required setup.
Connect eligible Merchant Center accounts and start selling the service under your brand.
Who it is for
Add a high-margin recurring product to Google Ads management. Improve client retention and strengthen your expert positioning with a visible, measurable service.
Run a dedicated CSS brand across multiple stores, markets or business units while keeping one fixed subscription and centralised infrastructure.
Simple pricing
No per-client fees, no product limits and no click commission. Select the billing option and continue to secure Stripe Checkout.
A 30-day trial/onboarding path can be arranged before the full commercial rollout. Contact us to confirm eligibility and implementation details.
Feedve White Label CSS
Billed annually: €1,500
Secure payment handled by Stripe. Prices shown exclude applicable VAT.
FAQ
It is a Comparison Shopping Service and product-comparison environment launched under your brand. Eligible client stores can use it for Google Shopping ads while your agency presents the service as part of its own offer.
No. The White Label plan is designed around one fixed subscription with an unlimited number of client stores and products, subject to the programme’s technical and eligibility requirements.
The service is prepared in a white label model. Your selected CSS brand is used in the client-facing environment and next to eligible Shopping ads. Feedve remains the technology and operational provider.
No. The CSS switch is an administrative Merchant Center change. Existing Google Ads campaigns, history and optimisation data remain in place.
The timeline depends on the selected domain option, delivery of brand details and Merchant Center readiness. A standard implementation is usually completed after the required information and access have been provided.
Yes. You control your commercial model, resale price and client communication. Feedve charges the agreed fixed White Label subscription.
Lower costs for clients. Stronger retention for your agency. One infrastructure that scales with every new store.
White Label CSS is a price comparison service operating within the Google CSS (Comparison Shopping Service) programme under an agency’s or retailer’s own brand instead of the default “By Google” label. It enables product ads to run in Google Shopping with a lower cost per click and the agency’s branding displayed alongside each client’s ads. To avoid confusion from the outset, this is not about white-labelling an application interface with CSS as in Cascading Style Sheets. This guide focuses exclusively on Google CSS as an advertising channel, explaining how the mechanism works, when it makes financial sense and when it does not.
A White Label CSS is a price comparison service owned by an agency or retailer and approved within the Google CSS programme. Instead of the default “By Google” label beneath a Shopping ad, the name of the comparison service owner appears, while the cost per click can decrease. The entire mechanism operates through Google Ads and Google Merchant Center, not through a website’s source code.
The abbreviation “CSS” has two meanings, and search engines often mix them together. The first is Cascading Style Sheets, which developers use to control the appearance and branding of websites and applications. The second is Comparison Shopping Service, Google’s programme for price comparison services. White Label CSS in this article refers exclusively to the second meaning.
The distinction has practical consequences. When you want to change colours and logos in a SaaS dashboard, you need a developer and CSS variables. When you want lower-cost clicks in Google Shopping and your own brand displayed on product ads, you need the Google CSS programme. These are two separate concepts connected only by the same three-letter abbreviation.
PPC agencies managing multiple e-commerce clients usually gain the greatest value from White Label CSS. An agency launches one comparison service under its own domain and connects the Merchant Center accounts of all participating clients. As a result, the agency’s name can appear on thousands of product ads, while every connected client benefits from a lower CPC.
The second group consists of individual e-commerce retailers, which more often choose Branded CSS using their own store brand. Freelancers and affiliates can also participate, provided they manage a sufficient number of shops. The common requirement is simple: you must be running product campaigns in Google Shopping, otherwise the comparison service has nothing to support.
Consider an agency with ten e-commerce clients. It connects every account to one comparison service, reduces CPC for each client from day one and displays its own brand across all of their product ads. Previously separate accounts become one shared commercial asset for the agency.
Every product ad in Google Shopping includes a small “By” label identifying the comparison service through which the ad entered the auction. By default, it reads “By Google”. After implementing your own comparison service, your brand appears in this position, for example “By Your Agency”.
The field serves two purposes. First, it builds recognition because the owner’s name appears alongside every client ad. Second, it can generate free traffic: clicking the “By” link takes the user to the comparison service rather than the retailer, and that click is not charged. With White Label CSS, the field becomes a piece of advertising inventory controlled by your agency.
The Google CSS programme supports three main models. They differ in who owns the comparison service and who retains the margin associated with the cost per click. The default “By Google” model leaves that margin with Google. Branded CSS belongs to a retailer and displays the retailer’s brand on its own ads. White Label CSS belongs to an agency, whose brand can appear on the product ads of all connected clients. The selected model determines which name appears in the “By” field.
The differences are easiest to understand in one table. The ads themselves do not change. What changes is who owns the comparison service and who captures the benefit of the lower CPC.
| Feature | Default Google CSS | Branded CSS | White Label CSS |
|---|---|---|---|
| Comparison service owner | E-commerce retailer | Agency | |
| Name in the “By” field | By Google | Retailer’s brand | Agency’s brand |
| Who retains the CPC margin | Retailer | Agency and its clients | |
| Brand shown on client ads | No | Only the retailer’s own ads | All connected client ads |
| Best suited to | Getting started without a comparison service | A single retailer | An agency managing multiple accounts |
The default option is the starting point for every account. Moving to Branded CSS or White Label CSS unlocks the CPC advantage and proprietary branding in Google Shopping. Product ads look the same in every model; only the “By” label and the beneficiary of the click-cost saving change.
The decision depends on the structure of the business. When you operate one store and want to strengthen your own brand on your own ads, Branded CSS is the natural choice. It is generally easier and less expensive to maintain, and your store appears twice in the ad: in the product listing and in the “By” field.
When you manage product campaigns for multiple clients, White Label CSS offers a stronger advantage. One comparison service can support every account, while the agency’s brand gains visibility alongside each client’s ads. White Label CSS then becomes not only a way to reduce CPC, but also a marketing tool for the agency itself. The dividing line is not absolute, but the more stores an agency manages, the stronger the case for the white-label model. In practice, agencies with five or more active e-commerce clients often choose White Label CSS because the cost of the comparison service is distributed across multiple accounts.
When product ads run through your own comparison service instead of the default Google CSS route, you avoid the additional margin Google applies to the click cost. This difference is the core value of White Label CSS. Comparison service providers commonly claim CPC reductions of up to around 20%, which means that the same budget can win more auctions, generate more impressions and drive more sales through Google Shopping.
When a Shopping ad enters the auction through the default route, Google adds its own margin to the bid. The final click can therefore cost more than the amount created solely by competition between advertisers. A proprietary comparison service in the Google CSS programme allows that margin to be recovered and used in the auction instead.
The effect is mathematical. If the Google margin increased click costs by several or more percentage points, removing it reduces CPC by a similar amount. Some providers claim benefits of up to 25%, while others refer to approximately 20%. With a fixed budget, a lower CPC translates directly into more traffic. A budget that previously purchased one thousand visits can purchase substantially more after the click cost decreases. This mechanism underpins the White Label CSS market.
The second benefit concerns traffic rather than bids. Clicking the “By” link below an ad takes the user to the comparison service instead of the retailer and does not trigger a paid ad click. With White Label CSS, that traffic reaches your own domain rather than an external intermediary.
For an agency, this creates a free brand-awareness channel. Every client ad becomes a carrier of the agency’s name, and some users click the label and land on its comparison service. The scale depends on campaign volume, but the traffic itself is not charged because Google does not count these interactions as paid clicks.
The lower-CPC mechanism is one thing; the real account result is another. In Google Shopping, the final return on ad spend matters more than provider claims. In one Double Digital fashion e-commerce campaign using Google Ads and Performance Max, ROAS reached 1,066%, sales increased by 280% and CPA decreased by 40%. In another impulse-purchase category involving toy vending machines, ROAS exceeded 1,000%, up from an initial 300%, while sales increased by 229% and conversion cost fell by 64%.
Results of this kind come from combining the right campaign structure, a clean product feed and control over click costs, with a proprietary comparison service being one of the supporting elements. As a Google Premier Partner 2026 and a top 3% agency in Poland, Double Digital treats White Label CSS as one optimisation lever, not a magic switch. The figures above come from real advertising accounts, not simulations.
For an agency, White Label CSS is not only a way to reduce clients’ CPC. It can become a separate product and recurring revenue stream. The agency displays its own brand on the product ads of all connected clients, strengthens its position as a Google Shopping specialist and charges a recurring fee for access to the comparison service. The service can be included in a retainer or sold separately, with the margin remaining with the agency.
The agency’s name displayed alongside each client’s product ad acts like a permanent banner. Depending on campaign volume, users may see “By Your Agency” hundreds of thousands of times per month. These are brand impressions that do not require a separate display media budget.
This visibility can translate into leads. Other store owners see ads carrying the agency’s name and associate the brand with expertise in Google Shopping. Some contact the agency directly because White Label CSS positions it as a specialist in product campaigns. Client acquisition becomes more efficient when proof of competence circulates throughout the market without additional media spend.
Monetisation follows a straightforward model. The client benefits from a lower CPC, while the agency charges a fixed monthly fee for access to the comparison service. The difference between the cost of maintaining one comparison service and the combined subscriptions paid by all clients becomes the agency’s margin. The economics improve as more stores are connected because infrastructure costs remain relatively stable while recurring revenue increases with each account.
A reliable comparison service provider should never contact an agency’s clients directly or attempt to upsell them. This must be verified before signing an agreement because it determines whether White Label CSS strengthens the agency’s business or exposes it to unnecessary risk. A good provider remains invisible infrastructure, while the commercial relationship and margin stay with the agency.
The risk increases when the provider is itself an agency or offers competing services. In that situation, your clients appear in a competitor’s database, creating an opportunity for contract takeover. Ask directly about the provider’s policy on contacting end clients and whether it operates in the same service market. Also verify who owns the comparison service domain. When ownership remains with the agency, the agency controls a genuine asset rather than merely renting someone else’s infrastructure.
White Label CSS is not suitable for every business. When you do not run product campaigns in Google Shopping, manage fewer than the required number of stores or operate with a low monthly Shopping budget, the setup and subscription costs may exceed the CPC savings. Profitability should be calculated before implementation, not afterwards.
The calculation is straightforward. The saving generated by White Label CSS is a percentage of Google Shopping spend, while the cost consists of a fixed setup fee and a recurring subscription. As long as the percentage saving is lower than the monthly fee, the service operates at a loss. The break-even point improves as product campaign spend increases.
Across accounts managed by Double Digital, a proprietary comparison service starts to make sense with regular monthly Shopping expenditure rather than isolated tests worth a few hundred PLN. The effect of the lower click cost is best evaluated through ROAS. There is no universal threshold because profitability depends on the industry, margin and auction competition. The principle remains the same: the larger and more stable the Shopping budget, the faster White Label CSS can pay for itself.
The comparison service must satisfy Google CSS programme requirements. A non-compliant provider can expose connected accounts to suspension. Retailers can lose CSS status when the comparison service violates programme guidelines, forcing campaigns back to more expensive clicks and creating operational disruption. When selecting a partner, ask about its compliance history and how often clients have encountered certification problems.
Also verify who owns the domain and the comparison service website. In some offers, the domain belongs to the client but the website itself cannot be transferred, creating dependency on the provider. Before committing to White Label CSS, review the terms covering compliance, transfer and termination. Those clauses determine whether the comparison service is your asset or merely a rented service that disappears when you change partner.
Implementation follows several structured stages: select a provider that is a Google CSS partner, choose your own domain, populate the comparison service with offers from the required number of stores, complete Google’s audit and certification, and connect clients’ Merchant Center accounts. The technical work is usually completed faster than the Google review, which is why the end-to-end process can take several weeks. White Label CSS is launched once and can then be expanded by adding further accounts.
Regardless of the provider, the sequence is similar. First, you sign an agreement and specify the domain or subdomain where the comparison service will operate. The provider then builds the price comparison website and submits it for Google certification. After a successful audit, client accounts are connected and ads begin to serve with your label and the CPC advantage. The programme typically requires offers from several independent stores, so additional accounts may need to be included at launch when the agency’s own portfolio is too small.
An important detail is that switching the comparison service does not stop the campaigns. Accounts, feeds and budgets continue to run, including Performance Max campaigns; only the CSS assignment changes in the settings. When an organisation does not have the resources to manage product campaigns internally, the implementation can form part of a broader Google Ads and Shopping management service.
Before launch, prepare a domain or subdomain for the comparison service, your logo and brand colours, and a list of stores to be included. For each store, the provider will usually need the business name, address, account identifier and product feed. The cleaner the feed, the faster the audit and the fewer corrections will be required. Data is connected through Google Merchant Center, while ongoing comparison service management takes place in CSS Center.
| Item | Why it is needed |
|---|---|
| Domain or subdomain | The address where the comparison service will operate |
| Logo and brand colours | Branding for the website and the “By” field |
| List of stores | Offers required for comparison service certification |
| Product feed for each store | Product data used by Google Shopping |
| Access to CSS Center | Management of connected accounts and CSS Partner status |
Data quality has a direct impact on performance. Even the best comparison service cannot compensate for a neglected product feed. Before connecting accounts, resolve Merchant Center errors and compare available providers and tools carefully, including the level of control they offer over the comparison service and its data.
The Google CSS (Comparison Shopping Service) programme was created after the European Commission’s 2017 decision that Google had favoured its own comparison shopping service in Google Shopping. In response, Google opened Shopping auctions to external comparison services and introduced a difference in the effective click cost. The White Label CSS market developed from this structure, allowing agencies and retailers to operate proprietary comparison services.
This background explains why the CPC advantage is structural rather than merely promotional. A lower click cost is not a temporary provider discount. It results from the market framework introduced after the European Commission’s decision. As long as that framework remains in force, operating through an approved comparison service remains a legitimate way to access lower-cost clicks.
For advertisers, the conclusion is straightforward. White Label CSS is not an unofficial loophole that Google is expected to close. It is part of the platform’s formally established ecosystem. Using a proprietary comparison service is therefore compliant when the provider follows programme requirements. Understanding this context also makes it easier to distinguish reliable partners from providers making promises that conflict with Google’s policies.
The CSS market has matured. In the early years, simply using an external comparison service created a stronger competitive advantage because adoption was limited. Today, participation alone is not enough. Product feed quality, campaign structure and provider selection determine the result. White Label CSS remains a valuable tool, but it should be treated as part of professionally managed Google Shopping campaigns rather than a standalone guarantee of performance.
Yes. White label is a legal business model in which technology supplied by one company is sold under another company’s brand. In Google Shopping, a proprietary comparison service operates within the official Google CSS programme and is reviewed by Google. Safety depends on whether the provider complies with programme guidelines, which makes partner selection critical.
White Label CSS is a price comparison service operating within the Google CSS programme under an agency’s or retailer’s brand rather than the “By Google” label. It enables product ads to run in Google Shopping with a lower cost per click and proprietary branding. It is an advertising channel, not interface white-labelling with Cascading Style Sheets.
The difference concerns ownership of the comparison service. Branded CSS belongs to an e-commerce retailer and displays that retailer’s brand on its own ads. White Label CSS belongs to an agency and displays the agency’s brand across the product ads of all connected clients. A retailer with one brand usually chooses Branded CSS, while an agency managing multiple accounts typically chooses White Label CSS.
Pricing usually combines a one-off setup fee with a monthly subscription for maintaining the comparison service. Rates vary between providers and depend on the number of connected stores and the scope of the service. Instead of comparing price lists alone, calculate the break-even point: the CPC saving generated by your Shopping budget must exceed the recurring fee.
Technical work on the provider’s side usually takes several days, but Google’s audit and certification extend the full timeline. In practice, several weeks may pass between submission and full launch. Having the domain, store details and product feeds prepared in advance can materially shorten the process.
No. Changing the comparison service does not interrupt campaigns. Accounts, feeds and budgets continue running because only the CSS assignment in the account settings changes. After Google approval, the ads continue to serve with your label in the “By” field and the lower CPC structure.