Lightspeed returning customer bidding in Meta: agent skill
The set-up-lightspeed-meta-returning-customer-bidding agent skill: send repeat orders from Lightspeed to Meta as PMReturningCustomer through the Meta Conversions API with Advanced Matching, and optimise a campaign on a custom conversion.
set-up-lightspeed-meta-returning-customer-bidding sets up returning customer bidding for Lightspeed in Meta with Product Metrics. Send repeat orders from Lightspeed to Meta as PMReturningCustomer through the Meta Conversions API with Advanced Matching, and optimise a campaign on a custom conversion. It follows the guide Lightspeed returning customer bidding in Meta.
The skill
Read the full file on GitHub (with its references) or at /.well-known/agent-skills/set-up-lightspeed-meta-returning-customer-bidding/SKILL.md, or install it with:
pnpm dlx skills add product-metrics/skills \
--skill set-up-lightspeed-meta-returning-customer-biddingIn 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
- “Set up a retention campaign that values repeat orders.”
- “Bid on returning customers in Meta.”
- “Is the conversion sent for every repeat order?”
What it does
- Reads where your setup stands and skips every step that is already done.
- Checks how your store’s orders are counted as new or returning.
- Creates the returning customer conversions and has you bid on one in the campaign for returning customers in Meta.
- Checks a test order from a customer who ordered before.
- Tells you which value Meta 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:
| Reference | Built from |
|---|---|
references/returning-customer-bidding.md | Lightspeed returning customer bidding in Meta |
references/connect-lightspeed.md | Lightspeed eCom server-side tracking and profit bidding (POAS) |
references/connect-meta.md | Meta Conversions API and Advanced Matching |
references/working-with-product-metrics.md | CLI for agents |
Related skills
set-up-lightspeed-meta-conversions-api: Server-side tracking for Lightspeed in Metaset-up-lightspeed-meta-advanced-matching: Advanced Matching for Lightspeed in Metaset-up-lightspeed-meta-new-customer-bidding: New customer bidding for Lightspeed in Metaset-up-lightspeed-meta-poas-bidding: POAS and ROAS bidding for Lightspeed in Metaset-up-lightspeed-meta-ltv-bidding: LTV bidding for Lightspeed in Metaset-up-lightspeed-google-ads-returning-customer-bidding: Returning customer bidding for Lightspeed in Google Adsbid-on-profit: check POAS or ROAS bidding on any storeproduct-metrics: picks the right skill for any store and channel- All skills by platform and channel