The Unsexy but Most Powerful Conversions API Setup

Why "Unsexy" Actually Means Most Powerful

Everyone wants to talk about creative and targeting. Almost no one wants to talk about tracking, it is technical and unglamorous, and that is exactly why it is an edge. In 2026, browser signals leak from iOS, cookie blocking, and ad blockers, so the pixel alone misses a big chunk of your conversions. The Conversions API sends purchase data server-to-server, straight to Meta, so the algorithm sees the full picture and optimizes on real revenue.

Here is why the "unsexy" route is actually the most powerful one. Dedicated providers like Stape do server-side tracking well, but that is all they do, and they charge a recurring subscription for it. Building it on n8n costs a fraction of that because you self-host it, and you get far more flexibility: the same tool that sends your conversions can also fire WhatsApp messages, sync leads to your CRM, and run the rest of your business automations. You are not renting one narrow feature, you own a platform that does this and everything else.

And you do not need to be technical to set it up: Claude Code handles the code and debugging for you.

When You Need This Setup

If your site runs on Shopify or WordPress, Meta's ready-made partner connection in Events Manager is the easier route, use that. This setup is for everything the ready-made connections miss:

• Custom-built websites with no plugin to install.
• Razorpay (or other) payment pages where the sale happens outside your site builder.
• Lead forms that save to Google Sheets or a CRM instead of a store.
• Sales that close on WhatsApp or a phone call, marked as won in a sheet or CRM.
• Agencies who want one setup they can repeat for every client.

The 3 Ingredients, Mapped Out

The whole setup is just three pieces connecting in one direction: your sale → n8n (wired up with Claude Code) → Meta's Conversions API. Click each ingredient to see its role and exactly what you need:

Browser-Side vs Server-Side: Who Sends the Sale?

There are two ways n8n can hear about a sale. Tap each one to see why this guide only uses the second:

Who Tells n8n About a Sale

Step 1: Get Your Meta Keys

Meta is the destination, the place your server-side events are sent so campaigns can optimize. You generate your keys inside Events Manager. You need two values, plus a Business Manager account:

• Dataset / Pixel ID: the ID of the dataset your events belong to (Events Manager → Data Sources → your dataset → Settings).
• Conversions API access token: in that same Settings tab, find the Conversions API section, choose "Set up manually," and click Generate access token. Meta sets up a Conversions API system user for you, no app review required.

Copy the token the moment it appears, Meta does not show it again. If you lose it, you generate a new one.

Step 2: Plan Your Events With Claude

Before building anything, decide what to send. Ask Claude with the prompt below, changing the first sentence to match your business.

I sell a course through Razorpay and collect leads through a form on my website. Which Meta Conversions API events should I send, when should each one fire, and which customer details should each one include? Give me a table, and tell me which details must be hashed.

The Usual Event Plan

For most businesses, Claude comes back with something like this:

Step 3: Connect Razorpay to n8n

The example uses a Razorpay checkout, the classic "no plugin exists" case. In this guide, your n8n lives at n8n.example.com; use your own address.

• In n8n: add a Webhook node as the trigger. Copy its production link, for example https://n8n.example.com/webhook/razorpay-capi.
• In Razorpay: go to Dashboard → Account & Settings → Webhooks → Add new webhook. Paste the n8n link, set a secret, and tick the payment.captured event.
• Check the signature first: Razorpay signs every call with your secret in the X-Razorpay-Signature header (HMAC SHA256 of the raw body). Ask Claude Code to add this check as the first step, so nobody else can send fake sales to your link.
• Convert the amount: Razorpay sends amounts in paise. Divide by 100 before sending the value to Meta, or your ₹2,499 sale shows up as ₹2,49,900.
• Expect repeats: Razorpay can send the same webhook more than once. Step 6 (the event ID) makes Meta ignore the repeats.

Step 4: Carry the Meta Cookies Through Checkout

Server-side has one catch: Meta matches a sale to the right ad much better when it also gets a few details from the customer's browser, and a payment webhook does not have them on its own.

• _fbp: a Meta cookie that says "this is the same browser Meta has seen before".
• _fbc: a Meta cookie that says "this person arrived from a Meta ad click".
• Browser info (the user agent): Meta requires it for website events.
• The page address where the purchase happened: also required for website events.

The fix is simple and still server-side. When your site's server creates the Razorpay order, the customer's request already carries those cookies and the browser info. Your server copies them into the order's notes, and when the payment is captured, Razorpay's webhook delivers them to n8n together with the email and phone. Nothing is sent from the browser to n8n.

Razorpay notes allow up to 15 fields of up to 256 characters each. Browser info can be longer than that, so split it across two fields (for example ua_1 and ua_2) and have Claude Code join them back in n8n. The _fbc cookie only exists when someone arrived from an ad click, so if it is missing, that is normal: send what you have.

Step 5: Let Claude Code Build the Mapping

This is the step that makes the whole thing doable if you are not a developer. Claude Code is Anthropic's agentic coding assistant, and it writes the n8n code node that turns a Razorpay payment into a Meta event. You can start from the ready-made n8n CAPI template and let Claude Code adapt it.

Paste a real Razorpay webhook sample (the JSON n8n shows for the Webhook node) into Claude Code along with the prompt below, so it writes the mapping against your actual field names instead of guessing. When Meta rejects an event, paste the error back and Claude Code fixes it. One rule from Meta worth knowing: events older than 7 days are rejected, so the workflow should send each sale as soon as it arrives.

Wiring up CAPI is one piece of a much bigger shift, running the whole ad account with AI as the method, which is what our AI-first performance marketing course is built around. If you would rather have an expert check whether your pixel and Conversions API are sending the right events, that is part of my Meta ads consultation.

Here is a sample Razorpay payment.captured webhook from my n8n Webhook node. Write an n8n Code node that turns it into a Meta Conversions API Purchase event:

- First, verify the X-Razorpay-Signature header (HMAC SHA256 of the raw body with my webhook secret). Stop if it does not match.
- event_name "Purchase", action_source "website", event_time = payment time in seconds, event_source_url = the page address from the order notes.
- event_id = the Razorpay order ID.
- Clean and SHA-256 hash the email (trim, lowercase) and phone (digits only, with country code 91).
- Send fbp, fbc and the browser user agent from the order notes as they are, not hashed. Join ua_1 and ua_2 if the user agent was split.
- value = amount divided by 100 (Razorpay sends paise), currency "INR".

Then show me the final JSON you would send, so I can check it before going live.

Step 6: Stop Meta Counting a Sale Twice

Keep your Meta Pixel on the site. It still catches browser events like page views and add-to-cart, and it reports the purchase too. Now Meta hears about the same sale twice: once from the Pixel and once from n8n.

Meta removes the duplicate when both reports carry the same event ID and the same event name, and arrive within 48 hours of each other. So:

• In the Pixel's Purchase event on your thank-you page, pass the Razorpay order ID as eventID.
• In n8n, send the same order ID as event_id, with the same event name, "Purchase".

Meta keeps one and drops the other. The same ID also stops Razorpay's repeated webhooks from being counted twice.

Step 7: Test It in Events Manager

Never go live without seeing a real event arrive:

• Get a test code: Events Manager → Data Sources → your dataset → Test Events. Copy the test code it shows.
• Add it to n8n: send it as test_event_code in the request, only while testing.
• Make a test payment on your checkout (a small real payment you refund, or Razorpay test mode while you build).
• Watch it arrive: the Purchase event appears in the Test Events window, received from the server. If the Pixel also fired, check that Meta shows the pair as deduplicated.
• Remove the test code before going live. Meta says it is only for testing.

Step 8: Read and Improve Event Match Quality

Event Match Quality is Meta's score out of 10, shown beside each event in Events Manager with a rating label. It tells you how well Meta can match your events to real people, and better matching means better optimization. A Purchase from a checkout, with email and phone, should be one of your best-scoring events. If it reads low, check these:

Does Sending Through Your Own n8n Server Count as "Third-Party"?

A question every agency asks: if a client's sales go to my n8n server and then to Meta, will Meta treat it as third-party or restrict the domain?

For Meta, no. Meta identifies your events by the client's dataset ID and access token, not by which server sends them. The event also carries the client's page address, so it belongs to the client's site. Agencies, Zapier and Shopify all send events on behalf of other businesses every day.

What does get a dataset restricted is the content of the events, not the sender:
• businesses in sensitive categories, such as health or finance, sending details Meta does not allow for them
• customer details sent unhashed, or tucked into page addresses and custom fields
• fake or duplicated purchases

The real "third-party" problem only appears in the browser: when a website's page sends events straight from the visitor's browser to another domain. That is exactly why this guide is server-side only.

Advanced: If a Browser Must Send Events to n8n

Sometimes you cannot avoid it, for example a page event that only exists in the browser. To a browser, clientsite.com sending to n8n.example.com looks like an outsider, so ad blockers may stop it and it cannot read the client's cookies.

The fix is to give your n8n server a second name under the client's domain, like track.clientsite.com. This is pointing, not forwarding: the browser looks up where track.clientsite.com lives in the internet's phonebook (DNS), then talks to your n8n server directly while still calling it track.clientsite.com. With a forward, the browser would end up visibly talking to n8n.example.com, which defeats the point.

Add one of these records in the client's domain settings:

Common DNS Mistakes

• Cloudflare error 1014, "CNAME Cross-User Banned": you see this when the client's CNAME points to a hostname that is proxied (orange cloud) in a different Cloudflare account. Use the A record instead, or Cloudflare for SaaS (custom hostnames), which is built for exactly this.
• No padlock for the new name: your n8n server must accept track.clientsite.com and hold a security certificate for it, or the browser shows a warning. Add the name to your web server settings (nginx or Caddy) and issue a free Let's Encrypt certificate. Caddy does it automatically.
• Changes are not instant: DNS updates usually work within minutes, but can take a few hours.

Privacy: You Are Handling Your Client's Customer Data

When raw customer emails and phone numbers reach your n8n server before they are hashed, you are processing your client's customer data. Under India's Digital Personal Data Protection (DPDP) Act, that needs to be covered:

• Agree it in writing with the client: what data you receive, why, and that you do not keep it.
• The client's privacy notice should say that purchase data is shared with advertising partners like Meta.
• Hash as early as possible in the workflow, and do not store raw details in n8n's execution logs longer than needed.

This is not legal advice. If the client is in a regulated industry, they should check with their own lawyer.

Keeping It Running

• Check Events Manager diagnostics weekly for warnings about missing parameters or failed events.
• Re-test after every site or checkout change, a renamed field can silently break the mapping.
• Watch the token: if events suddenly stop, check the access token first (revoked or removed system user) and generate a new one.
• Keep an eye on n8n: one self-hosted instance can run this workflow alongside every other automation you build. Make sure it is backed up.