# Hermoso: Meta Conversions API without code, from ChatGPT or Claude

> Machine-readable twin of https://hermoso.ai/blog/meta-conversions-api-without-code/. Generated from the shipped page. Do not edit by hand.
> Full agent guide: https://hermoso.ai/llms.txt · MCP: https://app.hermoso.ai/mcp

[Blog](https://hermoso.ai/blog/)

# Meta Conversions API without code: send sales and leads to your pixel from the app, ChatGPT or Claude

Send phone orders, CRM deals and leads to your pixel with the Meta Conversions API, no code. Hashed for you, with event match quality and automatic lead sending.

By the Hermoso team · Launched November 16, 2026 · Updated November 16, 2026 · 5 min read

Your Meta pixel misses sales. A phone order, a deal closed in your CRM, a checkout an ad blocker hid. Now Hermoso sends those to your own pixel through the **Meta Conversions API**, from the app, ChatGPT or Claude. No code, no server to set up, and every email and phone number is hashed for you before it leaves.

It also reads your pixel's health, event match quality included, and can send your Meta lead form leads back to Meta automatically. It costs no credits.

## What the Conversions API is for

The pixel in a browser only sees what happens in that browser. The Conversions API (people also call it Meta CAPI or the Facebook Conversions API) sends events to the same pixel from a server, so Meta can count sales and leads that never touched your website, and your ads can learn from them. Send the same event id your browser pixel sends, and Meta counts the purchase once, not twice.

## What is new

- **Send events.** Purchase, Lead, CompleteRegistration, AddToCart, InitiateCheckout, ViewContent, Contact, Subscribe, any other Meta standard event, or a custom name. Up to 1,000 events at a time, from the last 7 days (62 days for store visits).

- **Hashing done for you.** Pass plain values. Hermoso normalizes each one the way Meta's rules say (lowercase email, digits-only phone with its country code, two-letter state code and so on) and SHA-256 hashes it. A digest made the wrong way is accepted by Meta and matches nobody, so never hash anything yourself.

- **Pixel health.** The event match quality score out of 10 for each website event, which match keys arrive and how often, Meta's own list of problems with the fix for each, how much of your browser traffic the server also covers, deduplication coverage, and how fresh your uploads are.

- **Automatic sending.** Turn on Meta lead form leads, and each new instant form lead is sent back as a Lead, the way Meta's Conversion Leads setup describes. Turn on email leads who reply, and a lead who answers your outreach becomes a Lead too. Both run every hour.

- **Test events and Limited Data Use.** Pass the code from Events Manager's Test Events window to watch events arrive, and switch on Limited Data Use for US state privacy laws, per send or for the whole brand.

## What an event needs

Field What to give

Event name Purchase, Lead or any other standard or custom name

Where it happened website, phone_call, physical_store, chat, email, app, business_messaging, system_generated or other

When A date and time in the last 7 days (62 for physical_store)

Event id Something unique, such as the order number. The same id as your browser pixel's, so nothing counts twice.

Who At least one of: email, phone, name, date of birth, city, state, zip, country, your own customer id, a click id, or a Meta lead id. More keys, better matching.

Value Value and currency, required on a Purchase

A website event also needs the page address and the browser's user agent, because Meta requires both.

## A worked example

A furniture maker sells online and takes a lot of orders by phone. Those phone orders come from people who saw the Instagram ads, and Meta never hears about them. With Hermoso connected to Claude, the owner pastes three orders from yesterday and types:

Send these phone orders to my Meta pixel as purchases.

Hermoso sends each one as a Purchase with action source phone_call, the order number as the event id, the customer's email and phone hashed, and the order total in USD. The answer is Meta's own: "Meta received all 3 events on pixel Oakline Website. Received is not matched", because Meta matches each event on its side, and matched events are the ones that count toward your ads. They show in Events Manager within about 20 minutes.

Next: How good is my pixel's match quality? The reply lists each website event with its score out of 10 and Meta's own suggestions, for example that more purchases would match with a phone number attached. The owner also runs instant form ads for custom orders, so they turn on automatic sending for Meta lead form leads. From then on, every new form lead goes back to Meta as a Lead every hour, with nothing to remember.

## Set it up in the app

- **Connect Meta** under Connectors and tick the ad account that owns the pixel under Manage accounts. The pixel must be on an ad account you ticked, and the person who connected Meta needs access to that pixel in their Meta business. [Connect Meta here](https://app.hermoso.ai/?src=blog-meta-conversions-api-without-code&connect=meta).

- **Choose Conversions API** on the Meta card and pick your pixel.

- **Tick the sources to send automatically** (Meta lead form leads, email leads who reply), choose Limited Data Use, tick the consent box and press Save. Each source stays off until you do this.

- **Send one-off events**, like phone orders or closed deals, by asking the Studio.

Your customers need to have been told, and to have agreed where the law requires it, that their details may be shared with Meta. The consent box is you confirming that.

## Or ask ChatGPT or Claude

With Hermoso connected to ChatGPT or Claude, one sentence does it: Send today's two closed deals from my CRM to my Meta pixel as leads, with their emails. The agent uses `send_meta_conversions`, `meta_dataset_quality` for pixel health and `set_meta_conversions_auto` for automatic sending. They sit in Hermoso's ads tools, and an agent can always reach them with `find_tools`.

## More

Every field and the hashing rules: [the Meta Conversions API docs](https://hermoso.ai/docs/meta-conversions/). Meta in Hermoso: [the Meta channel page](https://hermoso.ai/channels/meta/). The browser pixel itself: [install the Meta Pixel and other ad pixels for you](https://hermoso.ai/blog/install-tiktok-pixel-linkedin-insight-tag-meta-pixel/). The short version is in the [changelog](https://hermoso.ai/changelog/meta-conversions-api/).

## Questions people ask

### What is the Meta Conversions API?

It sends events such as purchases and leads to your Meta pixel from a server instead of a browser, so Meta can count sales the browser pixel misses, like phone orders or deals closed in a CRM.

### Do I need a developer to set up Meta CAPI?

Not with Hermoso. Connect Meta, tick the ad account that owns the pixel, and send events from the app, ChatGPT or Claude, or turn on automatic sending for lead form leads.

### How do I improve event match quality?

Send more ways to match each person: email, phone with the country code, name, city and zip, plus the click id and browser id for website events. Hermoso's pixel health check lists Meta's own problems and the fix for each.

### Will a purchase be counted twice if both the pixel and the Conversions API send it?

Not when both send the same event id. Meta keeps one and drops the duplicate.

### Do I have to hash emails before sending them?

No. Pass plain values and Hermoso normalizes and hashes them the way Meta requires. A value hashed the wrong way is accepted by Meta and matches nobody.
