Lightspeed Meta Conversions API Advanced Matching: agent skill
The set-up-lightspeed-meta-advanced-matching agent skill: send hashed customer information from Lightspeed orders with every Meta Conversions API event (Advanced Matching), only when the visitor allowed ad user data.
set-up-lightspeed-meta-advanced-matching sets up Advanced Matching for Lightspeed in Meta with Product Metrics. Send hashed customer information from Lightspeed orders with every Meta Conversions API event (Advanced Matching), only when the visitor allowed ad user data. It follows the guide Lightspeed Meta Conversions API Advanced Matching.
The skill
Read the full file on GitHub (with its references) or at /.well-known/agent-skills/set-up-lightspeed-meta-advanced-matching/SKILL.md, or install it with:
pnpm dlx skills add product-metrics/skills \
--skill set-up-lightspeed-meta-advanced-matchingIn Claude Code, the product-metrics plugin adds every Product Metrics skill with the MCP server: /plugin install product-metrics --marketplace product-metrics/skills.
When an agent uses it
- “Our Meta event match quality is stuck around 5.”
- “Set up Advanced Matching for my Lightspeed store.”
- “Which customer fields go to Meta with each purchase?”
What it does
- Reads where your setup stands and skips every step that is already done.
- Checks that server-side tracking to Meta is live first.
- Sets the consent banner, because customer data is only sent with the visitor’s consent.
- Sends a test event and checks an order carries the hashed customer fields.
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 and the rules for working with Product Metrics (CLI for agents has the long form), 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/advanced-matching.md | Lightspeed Meta Conversions API Advanced Matching |
references/connect-lightspeed.md | Lightspeed eCom server-side tracking and profit bidding (POAS) |
references/connect-meta.md | Meta Conversions API and Advanced Matching |
Related skills
set-up-lightspeed-meta-conversions-api: Server-side tracking for Lightspeed in Metaset-up-lightspeed-meta-new-customer-bidding: New customer bidding for Lightspeed in Metaset-up-lightspeed-meta-returning-customer-bidding: Returning 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-enhanced-conversions: Enhanced Conversions for Lightspeed in Google Adsset-up-lightspeed-chatgpt-ads-customer-matching: Customer data matching for Lightspeed in ChatGPT Adscheck-tracking: check every part of tracking and find a test orderproduct-metrics: picks the right skill for any store and channel- All skills by platform and channel