Skip to content
Google Ads

Lightspeed POAS bidding: Google Ads conversion tracking with profit: agent skill

The set-up-lightspeed-google-ads-poas-bidding agent skill: send profit from Lightspeed orders to Google Ads as a conversion action and bid on it with a target ROAS (POAS bidding).

set-up-lightspeed-google-ads-poas-bidding sets up POAS and ROAS bidding for Lightspeed in Google Ads with Product Metrics. Send profit from Lightspeed orders to Google Ads as a conversion action and bid on it with a target ROAS (POAS bidding). It follows the guide Lightspeed POAS bidding: Google Ads conversion tracking with profit.

The skill

Read the full file on GitHub (with its references) or at /.well-known/agent-skills/set-up-lightspeed-google-ads-poas-bidding/SKILL.md, or install it with:

pnpm dlx skills add product-metrics/skills \
  --skill set-up-lightspeed-google-ads-poas-bidding

In Claude Code, the product-metrics-lightspeed plugin adds it with the MCP server: /plugin install product-metrics-lightspeed --marketplace product-metrics/skills.

When an agent uses it

  • “Switch my Google Ads campaigns from ROAS to POAS.”
  • “What target ROAS should I start with on profit?”
  • “Why are my profit conversions empty?”

What it does

  1. Reads where your setup stands and skips every step that is already done.
  2. Activates your additional costs, which profit needs.
  3. Has you bid on the profit value in Google Ads.
  4. Suggests a starting target: your campaign’s current POAS × 100, where 100% is break-even. One campaign first.
  5. Tells you which value Google Ads bids on now and what is left for you.

The agent works through the productmetrics CLI or the MCP server. Steps in your store admin or ad platform stay with you: the agent gives you the exact labels and waits until you are done. All conversion actions it creates are secondary, as Product Metrics creates them; choosing which one a campaign bids on is your step.

What’s in it

The skill is a short SKILL.md with the workflow, plus reference files the agent reads only when it needs them. Each reference is built from a page in these docs:

ReferenceBuilt from
references/poas-bidding.mdLightspeed POAS bidding: Google Ads conversion tracking with profit
references/connect-lightspeed.mdLightspeed eCom server-side tracking and profit bidding (POAS)
references/connect-google-ads.mdGoogle Ads server-side conversion tracking
references/working-with-product-metrics.mdCLI for agents