Server-side tracking with the Meta Conversions API on any website with Cloudflare: agent skill
The set-up-cloudflare-meta-conversions-api agent skill: send every purchase from your website to Meta from the server through the Meta Conversions API, with Advanced Matching and the script served from your own domain.
set-up-cloudflare-meta-conversions-api sets up server-side tracking for any website on Cloudflare in Meta with Product Metrics. Send every purchase from your website to Meta from the server through the Meta Conversions API, with Advanced Matching and the script served from your own domain. It follows the guide Server-side tracking with the Meta Conversions API on any website with Cloudflare.
The skill
Read the full file on GitHub (with its references) or at /.well-known/agent-skills/set-up-cloudflare-meta-conversions-api/SKILL.md, or install it with:
pnpm dlx skills add product-metrics/skills \
--skill set-up-cloudflare-meta-conversions-apiIn Claude Code, the product-metrics-cloudflare plugin adds it with the MCP server: /plugin install product-metrics-cloudflare --marketplace product-metrics/skills.
When an agent uses it
- “Set up the Meta Conversions API for my website.”
- “Meta reports far fewer purchases than we really have.”
- “Send website purchases to Meta from the server.”
What it does
- Reads where your setup stands and skips every step that is already done.
- Connects your website and Meta if they aren’t connected yet.
- Turns on server-side tracking step by step: consent banner, test event and test order.
- Checks the test order arrived, then tells you what is live 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/server-side-tracking.md | Server-side tracking with the Meta Conversions API on any website with Cloudflare |
references/connect-cloudflare.md | Server-side tracking and profit bidding on any website (Cloudflare) |
references/connect-meta.md | Meta Conversions API and Advanced Matching |
references/working-with-product-metrics.md | CLI for agents |
Related skills
set-up-cloudflare-meta-advanced-matching: Advanced Matching for any website on Cloudflare in Metaset-up-cloudflare-meta-new-customer-bidding: New customer bidding for any website on Cloudflare in Metaset-up-cloudflare-meta-returning-customer-bidding: Returning customer bidding for any website on Cloudflare in Metaset-up-cloudflare-meta-poas-bidding: POAS and ROAS bidding for any website on Cloudflare in Metaset-up-cloudflare-meta-ltv-bidding: LTV bidding for any website on Cloudflare in Metaset-up-cloudflare-google-ads-conversion-tracking: Server-side tracking for any website on Cloudflare in Google Adsset-up-cloudflare-chatgpt-ads-conversions-api: Server-side tracking for any website on Cloudflare 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