Skip to content
Google Ads

Lightspeed POAS bidding: Google Ads conversion tracking with profit

Send profit from Lightspeed orders to Google Ads as a conversion action and bid on it with a target ROAS (POAS bidding).

Every paid Lightspeed order goes to Google Ads server-side with its profit (Product Metrics - Profit) and its revenue (Product Metrics - Revenue). The one you make primary is what your target ROAS bids on: POAS and ROAS bidding.

Prerequisites

  • Workspace admin in Product Metrics, with Pro (Full Signal Tracking). Google Ads needs Merchant Center connected.
  • Your Lightspeed eCom (C-Series) shop connected: a back-office administrator login (an API key can’t sign in), the shop’s cluster, hostname and numeric Shop ID, and an enabled API key with its secret that has Read on Content, Products, Customers and Orders, and Read and Write on Settings and Tracking. The shop can’t already be connected to another workspace, and it reads Active with Configuration is current before you link your property. See Lightspeed.
  • Your shop domain on Cloudflare, with its DNS record proxied (the orange cloud), and a workspace admin who signs in to Cloudflare once.
  • A Google login with access to the Google Ads client account your campaigns run in.

In the app

1. Connect your Lightspeed shop and Google Ads

Connect your store with Lightspeed, then connect the Google Ads client account that runs your campaigns with Google Ads.

Connect your store, step by step:

Open Ecommerce platforms

Go to Integrations → Ecommerce platforms and select Connect on Lightspeed.

Ecommerce platforms under Integrations, listing the supported store platforms with a Connect button on Lightspeed.

Start the setup

The Lightspeed page lists three steps: connect your store, verify the connection and link a property. Select Connect Lightspeed.

The Lightspeed page under Integrations → Ecommerce platforms: 0 of 3 steps done, step 1 Connect your store with the Connect Lightspeed button, then Verify the connection and Link a property.

Enter your shop details

Choose the Cluster, then enter the Store hostname, Shop ID, API key and API secret. You create the API key in the Lightspeed back office under Settings → Store Settings → Developers.

The Connect Lightspeed dialog: Cluster set to Europe, then empty Store hostname, Shop ID, API key and API secret fields, each with where to find it in the Lightspeed back office, including the API key permissions, and the Cancel and Connect Lightspeed buttons.

Connect the store

Select Connect Lightspeed. Product Metrics checks the key, saves the connection, registers its order webhooks and detects your shop language.

The Lightspeed page after Connect Lightspeed, with the store's connection, credential and installation status.
Example data.

Follow the setup guide

Select Setup guide for every step in the Lightspeed back office, including the permissions the API key needs.

The Lightspeed setup guide panel in Product Metrics: every step in the Lightspeed back office, including the permissions the API key needs.

Then connect Google Ads:

Connect Google

On Connect Google Ads and Merchant Center, select Continue as your Google account and sign in with the account that can see your Google Ads. Tick Google Ads on Google’s screen: Merchant Center connects with the same sign-in.

The Connect step of onboarding, Connect Google Ads and Merchant Center: Google Ads and Merchant Center both Not connected, a Use our manager account link for when you can't sign in with that Google account, and the Continue as sam@northwind-outfitters.example button.
Example data.

Pick the client account

Choose the Google Ads client account that runs your campaigns, not a manager account. The workspace is named after the account you pick.

The account step of onboarding: the Google Ads accounts the signed-in Google account can see, to pick the one Product Metrics should analyse.
Example data.

Already have a workspace? Open Integrations and select Connect Google Ads on the Google Ads row (Add account once one is connected). The same sign-in and account steps follow.

Integrations in Product Metrics: the required connections first, Google Ads and Merchant Center with your product feed, each row with its status and one action.
Example data.

You should see: Connection status, Credential status and Installation status read Active, Configured and Active, publication reads Configuration is current, and the gateway says Gateway setup complete; Product Metrics lists your Google Ads account under your store.

2. Create the conversion actions

First choose your consent banner: in Tracking → Configure consent, choose the banner your shop shows: OneTrust, Cookiebot, Usercentrics or Osano. The profit conversion needs the visitor’s analytics and ad user data consent. See Consent.

Open Tracking

Go to Integrations → Tracking. The checklist shows six steps: start by connecting your store, or use Cloudflare Tracking if you have no store platform.

Tracking in Product Metrics with the Complete your tracking setup checklist of six steps, starting with Connect your store.

Follow the next step

Once your store is connected and linked, the checklist opens the next open step. Each step says what it does.

The Complete your tracking setup checklist in Tracking: 3 of 6 essential steps completed, with Connect your store, Link the store to this property and Install storefront tracking ticked, and Configure consent open as step 4 with the consent platform still Not configured.

Configure consent

Under Configure consent, pick the cookie consent platform your storefront uses. The storefront script collects nothing until the visitor agrees.

The Configure consent step in the tracking checklist, with the list of consent platforms to choose from.

Then select Tracking → Create Google Ads conversions → Create 8 conversion actions: Conversion actions. This page uses Product Metrics - Profit and Product Metrics - Revenue.

Create Google Ads conversions

Under Create Google Ads conversions, select Create 8 conversion actions. Product Metrics manages one Google Ads conversion action per purpose; they start as secondary goals, and you choose the primary goal in Google Ads.

The Conversion actions page in Product Metrics, opened from Tracking: Not configured, 0 of 8 managed and the Create 8 conversion actions button. Below it, Customer types (New customer revenue and profit, Returning customer revenue and profit) and Order value (Order revenue, Order profit), each Missing with Google goal status Unknown, and the Lifetime value group.

You should see: every Product Metrics conversion action is created and linked.

3. Activate your additional costs

Product costs come from the cost price on each Lightspeed order line. Lightspeed doesn’t report payment fees, so those always come from External payment fixed cost and External payment (%). Everything else comes from your additional costs.

Then, under Tracking → Add your additional costs, check the defaults for your country, set Product cost fallback (%) and select Activate additional costs: Costs.

Add your additional costs

Product costs come from your store where it reports them. Under Add your additional costs, add shipping, handling, returns and payment fees, set Product cost fallback (%) and select Activate additional costs, so the profit conversions carry real profit.

The Add your additional costs step in Tracking, prefilled for your country: shipping, handling, returns and payment fee fields, a Product cost fallback (%) field and the Activate additional costs button.

You should see: the Profit tracking section says your additional costs are active.

4. Bid on profit

  1. In Google Ads, make Product Metrics - Profit primary and your old purchase action secondary (how).
  2. Set the campaign to Maximise conversion value with a target ROAS, written as a percentage: 100% is break-even; 150% keeps €0.50 profit per €1 of ad spend.

Moving a campaign from revenue to profit? Lower the target: when to switch to POAS.

You should see: in Google Ads, Goals → Conversions lists Product Metrics - Profit as primary.

5. Check it works

Place a test order, then open Tracking in Product Metrics: Check tracking works.

You should see: the badge next to Tracking reads Tracking active, and the test order arrives with its revenue and profit. Home shows Collecting until it compares the new actions with your current ones, 14 days after the first order.

Set it up with AI

Connect your assistant

First time? Add the Product Metrics MCP server to your assistant, then paste the prompt below.

In Claude, choose Add custom connector; in ChatGPT, Settings → Apps & Connectors. Paste this URL:

https://www.productmetrics.io/mcp

Claude Code: run this in your terminal.

claude mcp add --transport http product-metrics https://www.productmetrics.io/mcp

CodexAll clients and details →

Paste the prompt into your assistant.

Set up POAS bidding (bidding on profit) for my Lightspeed shop in Google Ads with Product Metrics. Check my setup status first, walk me through each open step, and give me the link when I need to click something.
Set up POAS bidding (bidding on profit) for my Lightspeed shop in Google Ads with Product Metrics. Check my setup status first, walk me through each open step, and give me the link when I need to click something.
Set up POAS bidding (bidding on profit) for my Lightspeed shop in Google Ads with Product Metrics. Use the Product Metrics MCP server, or the productmetrics CLI with --json and the Product Metrics skills if they are installed (run `productmetrics help agents` first), and tell me when a step needs me in a browser.
Set up POAS bidding (bidding on profit) for my Lightspeed shop in Google Ads with Product Metrics. Use the Product Metrics MCP server, or the productmetrics CLI with --json and the Product Metrics skills if they are installed (run `productmetrics help agents` first), and tell me when a step needs me in a browser.

How it works on Lightspeed

On LightspeedSent as
RevenueThe order’s revenueProduct Metrics - Revenue
Product costsThe cost price on each Lightspeed order lineTaken off profit
Payment feesYour additional costs (Lightspeed reports no payment fees)Taken off profit
Shipping, handling, returnsYour additional costsTaken off profit
ProfitRevenue ex tax − all costs; 0 for a lossProduct Metrics - Profit
RefundsYour store reports themProduct Metrics adjusts the conversion

Troubleshooting

ProblemFix
Orders arrive with revenue onlyA cost of the order is still unknown. Complete your costs under Profit tracking → Edit costs: an order is sent with profit only once every cost is known (profit rules).

FAQ

What if a Lightspeed product has no cost price?

Product Metrics takes the cost price on each Lightspeed order line first, then the cost of goods for the same SKU in your linked Merchant Center, then your Product cost fallback (%) of the line’s revenue. With none of these, the order goes to Google Ads with revenue only.

Where do payment fees come from on Lightspeed?

Lightspeed doesn’t report payment fees, so they always come from your External payment fixed cost and External payment (%) in your additional costs.

Should I keep my old purchase conversion in Google Ads?

Keep it as secondary. Only one purchase action should be primary, or purchases are counted twice. Product Metrics always sends both revenue and profit; only the primary action steers bidding.

What happens in Google Ads when an order is refunded?

When Lightspeed reports the refund, Product Metrics adjusts the order’s conversion in Google Ads.

Where next

On the website: POAS, target ROAS, POAS calculator, Product Metrics for Lightspeed

Developers: do the same with the CLI or the API.