Meta Conversions API GatewayHelloConversions
Meta's Conversions API Gateway copies your pixel's events to Meta, and GHL stages reach it only through a sender such as Stape's HighLevel app. GHL sellers get more from HelloConversions: it sends the stages you pick and captures GHL payments for revenue reporting.
By JJ ReynoldsUpdated
7-day free trial · Money-back guarantee
Short answer
For website events, yes. The gateway copies the events your Meta Pixel fires and sends them to Meta. GHL stages need a separate sender, such as Stape's HighLevel app, and payments need your own code or an upload. HelloConversions is the better route for a GHL seller. It sends your chosen stages to Meta, Google Ads and TikTok, and logs each event. The gateway suits website sales.
JJ Reynolds · Updated
Side by side
| What we compared | HelloConversions | CAPI Gateway |
|---|---|---|
| GoHighLevel connection | One-click OAuthYou authorize your GHL account by OAuth, with no API keys or webhooks to set up. | Page pixel, or POSTs you buildIt relays Meta Pixel events from your pages. Since v1.6.0 it also accepts CRM events POSTed to its endpoint. Stape's HighLevel app can feed a Stape-hosted gateway. |
| Sends GHL stage changes | Yes, stages you chooseYou pick which GHL pipeline stages are sent, and each one is mapped to an ad platform event when a contact moves. No GHL workflow is built per stage. | Only via a POST you buildThe gateway has no CRM trigger. Since v1.6.0 it accepts offline and CRM events POSTed to its events endpoint, so a stage change needs a sender you set up. |
| Reads GHL payments | Payments and invoicesGHL purchases, payments, subscriptions and invoice events (created, paid, refunded) feed revenue reporting. How deposits and refunds are valued for ad platforms is not documented. | Only via a POST or file uploadA payment reaches Meta only if something sends it: a server POST, or a CSV or S3 upload with value, currency and order ID. |
| Meta Conversions API | YesIncluded in Conversions Plus+. Events go server-to-server from GHL, mapped to Meta events such as lead, qualified_lead and purchase. | YesIt sends pixel events to the Conversions API from a server in your own AWS or GCP account, set up from Events Manager. Events set up in the Event Setup Tool aren't supported. |
| Google Ads offline conversions | Offline import + enhancedOffline conversion import matched by GCLID, plus enhanced conversions with hashed customer data, sent from GHL with revenue values. | NoMeta describes it as forwarding Meta Pixel events to the Meta Conversions API. Pipelines to other destinations are a Signals Gateway feature. |
| TikTok Events API | YesEvents go server-to-server from GHL, including pipeline stage changes, mapped to TikTok events such as SubmitForm, Contact and CompletePayment. | NoIt forwards events to the Meta Conversions API only. Meta's Signals Gateway is the gateway it documents for other destinations. |
| Sends hashed customer details | Email, phone, name, city, stateTaken from the GHL contact, hashed with SHA-256 and sent with every event. Sent is not the same as matched: the ad platform decides whether an event matches a person. | Pixel user data, opt-inAn off-by-default setting adds pixel user data to events: email, name, phone, city, state, gender and zip. Server POSTs carry the hashed fields you send. |
| Dedupes with the browser pixel | Yes, Meta and TikTok pixelsServer events are deduplicated against Meta and TikTok browser pixel events. The mechanism, such as a shared event ID, and any Google Ads deduplication are not documented. | YesMeta says the event_id deduplication key is generated and passed along automatically, so pixel and gateway copies of an event match. |
| Per-event delivery log | Payload and response statusEach sent event shows its destination, event type, parameters and the platform's response status. "Matched" means the platform accepted the event, not that it matched the person. | Event counts and success rateThe admin UI shows events received from the pixel and sent to the Conversions API. Meta's monitoring guide lists no per-event payload log. |
| What the bill scales with | GHL contactsPriced in bands by the total contacts in your GHL account, not by the number of events or conversions tracked. | Cloud or partner feesMeta says the only cost is the associated cloud resource or partner fees. It names no Meta fee. You host it on AWS or GCP, or with a partner. |
Facts about Meta Conversions API Gateway as of October 2026. The gateway's cells describe Meta's own product as Meta documents it. Stape's HighLevel app can feed a Stape-hosted gateway, and Stape has its own comparison page. Sources are listed at the end of this page. HelloConversions cells describe our own product.
7-day free trial · Money-back guarantee
A visitor fills in your funnel's opt-in
With HelloConversionsAn opportunity created in a stage you mapped is sent as a conversion when it's created. Hashed email, phone, name, city and state from the GHL contact ride along.
With CAPI GatewayIf that page's Meta Pixel runs through the gateway, the event the pixel fires gets a server copy for Meta. The two share an event_id, so Meta can dedupe them.
They grab a slot on your GHL calendar
With HelloConversionsHelloConversions sends Booked the moment the opportunity reaches it, if Booked is on your list. Nothing has to be built in GHL to send it.
With CAPI GatewayA pixel event on the booking page gets the same server copy, if that page fires one. The opportunity's move to Booked happens in GHL, so it reaches the gateway only through a sender such as Stape's HighLevel app.
A rep marks the lead qualified
With HelloConversionsQualified goes out when the opportunity moves, for instance as qualified_lead in Meta or an offline conversion in Google Ads.
With CAPI GatewayThe gateway has no CRM trigger. A sender has to deliver it, such as Stape's app or your own server POSTing the hashed fields you choose.
A $300 deposit is paid in GHL
With HelloConversionsHelloConversions captures the $300 GHL payment for revenue reporting. Purchase events can go to Meta, Google Ads and TikTok. How a deposit is valued there isn't documented.
With CAPI GatewayMeta hears about it only if you send it. That means a POST from your own server, or a CSV or S3 upload with value, currency and order ID.
The $700 balance is paid
With HelloConversionsGHL's paid invoice for the $700 is captured for revenue reporting too. Purchase events can go to Meta, Google Ads and TikTok. How a balance is valued there isn't documented.
With CAPI GatewayThe balance needs the same POST or upload as the deposit. How a balance is valued at Meta isn't documented.
You give back $100
With HelloConversionsThe refunded invoice event is captured for revenue reporting. Purchase events can go to Meta, Google Ads and TikTok. How a partial refund is valued there isn't documented.
With CAPI GatewayNothing about the refund reaches the gateway on its own. How a partial refund is valued at Meta isn't documented.
Where HelloConversions is ahead
The gateway has no CRM trigger. It takes CSV and S3 uploads, and since version 1.6.0 it also accepts CRM events POSTed to its endpoint. So a GHL stage change or payment reaches the gateway only through a POST or a file upload. Stape's HighLevel app can send stage changes to a Stape-hosted gateway, but payments still need a sender you build or an upload. HelloConversions connects to GHL by OAuth, sends the stages you pick and captures GHL payments and invoices for revenue reporting.
Where HelloConversions is ahead
Meta describes the gateway as forwarding Meta Pixel events to the Meta Conversions API. It documents other destinations under a separate product, Signals Gateway. HelloConversions sends GHL conversions to Meta, to Google Ads as offline conversions with enhanced conversions, and to TikTok's Events API.
Where HelloConversions is ahead
The gateway's admin UI shows totals: events received from the pixel, events sent to the Conversions API and a success rate. Meta's monitoring guide adds Events Manager charts and Event Match Quality, with no per-event payload log. In the HelloConversions event-by-event log, each event shows its destination, type, parameters and the platform's response status. A "Matched" row means the platform accepted the event. Read it as a receipt, not proof that Meta found the person or credited the sale.
Where HelloConversions is ahead
The gateway's matching setting is off by default. Switched on, it adds what the pixel collected, such as email, name, phone, city, state, gender and zip. A sale closed on the phone never fires the pixel, so this setting adds nothing to it. HelloConversions takes email, phone, first and last name, city and state from the GHL contact and hashes each with SHA-256 before sending.
Where CAPI Gateway is ahead
Sales that close on your own website, such as an online checkout, are where Meta's own gateway leads. Each event your pixel code fires gets a server copy, deduped by an event_id the gateway creates and passes along. Meta says the only cost is the cloud resources or a partner's fee. HelloConversions starts from your GHL records instead, and its price rises with your GHL contact band.
A fair look
The Conversions API Gateway is a self-serve option in Meta's Events Manager. It runs on AWS EKS, AWS ECS Express or GCP, in a cloud account you hold, or with a hosting partner. Meta built it so performance marketers with some technical skill can set up the Conversions API with little developer help.
Each event your pixel code fires gets a server copy, with an event_id generated and passed along so Meta can dedupe the pair. Meta's troubleshooting guide notes one gap: events set up in the Event Setup Tool aren't supported. One instance can serve several pixels and domains, and it updates itself when the host admin agrees.
Since version 1.6.0 it also takes offline, app and CRM events that a server POSTs to it, and Meta documents CSV and S3 uploads. The gateway has no CRM trigger of its own, so GHL data needs a sender. Stape's HighLevel app can be that sender for stage changes on a Stape-hosted gateway, which our Stape comparison covers.
If you only need website events in Meta, Meta's overview points first to Conversions API with Meta. That's an Events Manager setting with nothing to host or maintain. The gateway fits a business whose sales happen on its own site and that wants its pixel events mirrored server-side.
Meta publishes no price for the gateway. As of October 22, 2026, its overview says the only cost is the cloud resource or partner fees. You pay your own AWS or GCP account, or a hosting partner.
Meta's ECS Express architecture page gives an estimate, not a price. It puts the base cost near $39.27 a month for 10 million events in us-west-2, using the AWS pricing calculator. It adds that your actual cost may vary with usage. Stape, one hosting partner, sells it instead as a plan priced per pixel.
Someone with admin access to the cloud account and the pixel does the setup. Meta's ECS Express page says that route takes about 25 minutes. Its main setup guide puts stack creation at 30 to 40 minutes and recommends a custom domain, which needs DNS access. Sending GHL data is a separate job: stages can go through Stape's HighLevel app on a Stape-hosted gateway, and payments need code or uploads.
HelloConversions is priced by the contacts in your GHL account, and events don't change it. Its lowest band is on the card below. The pricing page lists every band up to 80,000 contacts, and accounts above 100,000 get a quote.
The bill grows with: GHL contacts
Lowest published plan: $9/mo, under 500 contactsConversions Plus+, with unlimited event volume. The price rises with your GHL contact band, to $225/month at 80,000 contacts. 100,000+ contacts is quoted.
The bill grows with: Cloud or partner hosting fees
Not published as a Meta price. Meta's page says the only cost is the cloud resource or partner fees, paid to your cloud provider or a hosting partner.
Meta Conversions API Gateway pricing as of October 2026. Sources are listed at the end of this page.
7-day free trial · Money-back guarantee
Keep the gateway mirroring your website events, and link your GHL account to HelloConversions. The OAuth step to connect takes about 90 seconds. Mapping and testing each stage is the longer job.
Let the gateway keep the events your pixel fires, and give GHL stages and payments to HelloConversions. Map each stage to an event the pixel doesn't fire, such as qualified_lead, so one action isn't reported twice.
Take a real sale with a deposit and a balance. Find its pixel events in Meta's Events Manager, then its stage and purchase events in the HelloConversions log. Each event should arrive once.
If a script or file upload already sends GHL events to the gateway, stop it for each event HelloConversions takes over. Keep the gateway for as long as your website events need it.
No, it needs a sender. Stape's HighLevel app can send stage changes to a Stape-hosted gateway. Otherwise a server you build POSTs them to the endpoint version 1.6.0 added, since the gateway has no CRM trigger. HelloConversions sends the GHL stages you choose, with no sender or GHL workflow to build.
Meta publishes no price. Its overview says the only cost is the cloud resource or partner fees. Meta's estimate for an AWS ECS Express setup is about $39.27 a month at 10 million events in us-west-2. It says actual cost may vary with usage. Stape, one hosting partner, prices its hosted gateway per pixel.
It's Meta-only. Meta describes it as forwarding Meta Pixel events to the Meta Conversions API, and it documents other destinations under Signals Gateway, a separate product. HelloConversions sends GHL conversions to Meta, Google Ads and TikTok from one GHL connection.
Yes, if you send them. A server can POST events to its endpoint, or you can upload a CSV or S3 file with value, currency and order ID. Nothing in the gateway reads GHL payments on its own. HelloConversions captures GHL payments and invoices for revenue reporting.
Not for your GHL stages and payments. The gateway can still give your website's pixel events a server copy. If website events in Meta are all you need, Meta's overview suggests Conversions API with Meta, an Events Manager setting with nothing to host.
Yes. Meta says the gateway generates and passes the event_id deduplication key automatically, so a pixel event and its server copy match. HelloConversions also dedupes its server events against your Meta and TikTok pixel events.
This page is written by HelloConversions. Facts about Meta Conversions API Gateway come from public sources, checked in October 2026. Spot something out of date? Email hello@helloconversions.com. Product names are trademarks of their owners, and HelloConversions isn't affiliated with or endorsed by them.
Connect a sub-account, choose the pipeline stages that count as conversions, and check every event it sends in the delivery log.
7-day free trial · Money-back guarantee
HelloConversions