Make (DIY scenarios)HelloConversions
Make.com can watch GoHighLevel stage changes, invoices and orders, once you build a private app in the GHL Marketplace. If you sell through GHL, pick HelloConversions: it connects by one-click OAuth and captures GHL payments for revenue reporting.
By JJ ReynoldsUpdated
7-day free trial · Money-back guarantee
Short answer
Make.com reaches GoHighLevel stages and payments through its Watch Events trigger, after you build a private GHL Marketplace app. Make bills each run by the operations its trigger and modules use. HelloConversions lets a GHL seller skip that build. One OAuth connection sends your chosen stages and captures GHL payments for revenue reporting. Make still fits Meta Lead Ads stages, via its Conversions API for CRM app.
JJ Reynolds · Updated
Side by side
| What we compared | HelloConversions | Make |
|---|---|---|
| GoHighLevel connection | One-click OAuthYou authorize your GHL account by OAuth, with no API keys or webhooks to set up. | GHL app, OAuth + private appLocation or Company OAuth. The Watch Events trigger needs a private app you create in the GHL Marketplace, with webhook scopes and your own client ID and secret. |
| 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. | Invoice and order webhooksMake's scope list includes invoices and payments/orders. GHL documents webhooks such as InvoicePaid and OrderCreate, which Watch Events receives once you activate them. |
| 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. | Watch Events webhookTurn on the opportunities webhook scope in your private GHL app. GHL's OpportunityStageUpdate webhook fires on each stage change. Picking stages is scenario logic. |
| 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. | No click module in its listThe app lists call uploads, adjustments and an experimental enhancement module. Make's templates upload click conversions without naming a module. Needs a Standard Access token. |
| 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. | Send Events moduleThe Facebook Conversions API app sends events to your pixel. A separate Conversions API for CRM app sends lead stages, and Make doesn't bill its credits until February 2028. |
| TikTok Events API | YesEvents go server-to-server from GHL, including pipeline stage changes, mapped to TikTok events such as SubmitForm, Contact and CompletePayment. | YesThe TikTok Conversions app has a Send Event(s) module for your TikTok for Business account. |
| 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. | Run history, 30 days on CoreEach run's details show every module's output bundles. Detailed logs are kept 7 days on Free, 30 on Core to Teams and 60 on Enterprise. |
| 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. | Credits (module actions)Non-AI modules use 1 credit per operation, and a trigger run counts too. Make's example: a trigger returning 10 bundles to 3 modules uses 31 operations. |
| Lowest published paid 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. | $16/mo, 10,000 creditsCore, billed monthly, or $12/mo billed annually. The price rises with the credits you buy. |
| Free trial or free plan | 7-day free trial | Free plan, 1,000 credits1,000 credits a month, at least 15 minutes between scheduled runs and 7 days of detailed execution logs. |
Facts about Make (DIY scenarios) as of October 2026. Make's column assumes a scenario you assemble yourself, starting from Watch Events on a private GHL app. Its prices are US dollars at the 10,000-credit tier. Sources are listed at the end of this page. HelloConversions cells describe our own product.
7-day free trial · Money-back guarantee
Someone opts in through a GHL funnel page
With HelloConversionsIf the opt-in puts the opportunity in a stage you mapped, HelloConversions sends it, for example as a Meta lead event. HelloConversions hashes the contact's email, phone, name, city and state with SHA-256 and sends them along.
With MakeOnce the matching scope and webhook are switched on in your private app, Watch Events receives GHL's event. A scenario you build sends it to Meta through Send Events.
They book a call
With HelloConversionsBooked goes out the moment the opportunity lands there, as long as you picked that stage. HelloConversions needs no scenario or GHL workflow to send it.
With MakeGHL's OpportunityStageUpdate webhook fires when the deal moves to Booked. Picking out that stage is logic you add to the scenario, such as a filter.
A rep marks them qualified
With HelloConversionsQualified is sent as it happens: qualified_lead in Meta, and an offline conversion in Google Ads when the lead has a GCLID.
With MakeThe webhook fires again for Qualified. Make's Google app lists no click-conversion module, though Make's own templates upload click conversions.
They pay a $300 deposit
With HelloConversionsGHL's partial payment is captured on the HelloConversions side, for revenue reporting. Purchase events can go to Meta, Google Ads and TikTok. How a deposit is valued there isn't documented.
With MakeActivate GHL's InvoicePartiallyPaid webhook in your private app, and Watch Events can receive it. Your scenario then decides what value goes into Send Events.
They pay the $700 balance
With HelloConversionsThe $700 payment is captured as well, for revenue reporting. Purchase events can go to Meta, Google Ads and TikTok. How a balance is valued there isn't documented.
With MakeGHL's InvoicePaid webhook, called whenever an invoice is paid, starts the scenario again. Each module it runs uses credits again.
You refund $100
With HelloConversionsOn the HelloConversions side, the $100 refund 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 MakeMake's GoHighLevel docs don't mention refunds at all. Sending one to an ad platform would be a branch you design and test. How a partial refund is valued there isn't documented.
Where HelloConversions is ahead
Make's guide for its Watch Events trigger has 15 numbered steps. You create a private app in the GHL Marketplace, set Make's redirect URI, choose webhook scopes and enable them again under Auth. Then you publish the app, create a client ID and secret, and paste a Make webhook URL into its Default Webhook URL field. HelloConversions replaces all fifteen with a one-click OAuth authorization, and there are no API keys or webhooks. It takes about 90 seconds to connect, though defining your events and testing them takes longer.
Where HelloConversions is ahead
Credit to Make: it can see GHL payments, which a LeadConnector Zap has no trigger for. Make's scope list includes invoices and payments/orders, and once you activate webhooks such as InvoicePaid and OrderCreate, Watch Events receives them. Your scenario then turns each one into a Meta, Google Ads or TikTok event. Make's GHL docs describe moving events, not reporting revenue against spend. On the HelloConversions side, GHL payments and invoices are captured for revenue reporting. Its revenue dashboards put that revenue beside Meta and Google ad spend, with MER and cost per lead.
Where HelloConversions is ahead
Make's Google Ads Conversions app lists modules for call conversions, conversion adjustments and an experimental conversion enhancement, plus Make an API Call. No click-conversion module is listed. Make's own templates do upload click conversions, but they don't say which module they use. The app also needs a Google Ads developer token with Standard Access. In HelloConversions, the GHL connection sends offline conversions to Google Ads matched by GCLID, with no module to pick. Enhanced conversions with hashed customer data go too.
Make's scenario history shows each run, and its details show every module's output bundles. Detailed logs are kept 7 days on Free and 30 days on Core to Teams. That suits debugging a scenario. The HelloConversions per-event delivery log lists each event it sent, with destination, event type, parameters and the platform's response status. It also checks your UTMs and alerts you to sudden drops in event volume. A "Matched" status there means the platform took the event. It doesn't prove Meta matched the person.
Where Make is ahead
Make has a dedicated app for Meta's Conversions API for CRM, and its guide pairs it with the Facebook Lead Ads app. The app sends each lead stage as it's updated, including the first one. On legacy setups, the guide asks for a Meta pixel of type CRM. HelloConversions sends stage events to Meta but doesn't document this CRM route. Make also doesn't bill that app's credits from February 27, 2026 until February 2028. The GHL trigger and other modules still use credits. For Lead Ads stage events sent the CRM way, Make has the purpose-built module.
A fair look
Make is a visual scenario builder. A scenario starts from a trigger and passes data through modules, and Make bills in credits. Most module operations use 1 credit. Its GoHighLevel app manages contacts, opportunities, tasks, campaigns and notes, over a Location or Company OAuth connection.
For ad tracking, the useful part is the Watch Events trigger. Activate GHL webhooks such as OpportunityStageUpdate, InvoicePaid and OrderCreate in your private app, and Watch Events receives them. Make's Facebook Conversions API, Google Ads Conversions and TikTok Conversions apps can then pass those events on.
Meta Lead Ads advertisers also get a dedicated Conversions API for CRM app, which sends each lead stage as it's updated. If funnel events from GHL forms are all you need, GHL's own Meta Conversion API action may cover them without Make. Make suits a team with someone who likes to build scenarios, read their run history and keep them working.
Make bills in credits. As of October 22, 2026, its pricing page listed Core at $16 a month for 10,000 credits, in US dollars. Billed annually, Core is $12 a month. Pro is $28 and Teams is $51 at that tier, and each price rises with the credits you buy. The Free plan has 1,000 credits a month.
Most non-AI modules use 1 credit per operation, and a trigger run counts as one operation. In Make's own example, a trigger that returns 10 bundles to 3 modules uses 31 operations. Each GHL webhook starts a new run, so a sale with several payments runs the scenario several times.
HelloConversions doesn't count runs or operations. Its price is set by your GHL contact count. The pricing card below opens on the smallest band. The contact-band price list runs to 80,000 contacts. Past 100,000, HelloConversions quotes the price.
To size a Make plan, run the scenario on real GHL events for a week. Make shows the operations each module used, with the credits beside them. Scale that week to a month and pick the credit tier that covers it.
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: Credits (module actions)
USD, at the 10,000-credit tier. Paid prices rise with the credits you buy. Most non-AI module operations use 1 credit, and Make's AI features can use more.
Make (DIY scenarios) pricing as of October 2026. Sources are listed at the end of this page.
7-day free trial · Money-back guarantee
Leave every scenario on. Give HelloConversions OAuth access to the same GHL account, but hold back any stage or payment a scenario already sends.
Choose a GHL deal that has both a deposit and a balance paid. Compare each scenario run's output bundles with the matching HelloConversions events. Core keeps detailed run logs for 30 days, so check soon after the sale.
A purchase sent by both a scenario and HelloConversions can show up in Meta as two sales. Disable that module, or the route that leads to it, before you map the event in HelloConversions.
After that deal checks out, map your remaining stages and payments in HelloConversions. Then turn off the scenarios it replaces and deactivate the webhooks you switched on in the private GHL app.
Through Make's GoHighLevel app, whose modules connect by Location or Company OAuth. GHL events take more: Make's guide has you build a private app in the GHL Marketplace and enable webhook scopes. You then publish it and paste in a Make webhook URL. Make recommends Watch Events over the deprecated Watch Opportunities module.
Make's docs don't name one. Its Google Ads Conversions app lists call conversion uploads, adjustments and an experimental enhancement module, plus Make an API Call. Make's own templates upload click conversions without saying which module they use. The app needs a developer token with Standard Access. HelloConversions sends GCLID offline conversions and enhanced conversions from your GHL connection.
It depends on how many modules run. Most non-AI modules use 1 credit per operation, and each trigger run counts too. In Make's own example, a trigger returning 10 bundles to 3 modules uses 31 operations. As of October 2026, Core starts at $16 a month for 10,000 credits.
Not until February 2028. From February 27, 2026, Make doesn't bill the credits that app uses, as a promotion. The GHL trigger and other modules in the same scenario still use credits. The app sends lead stages to Meta's Conversions API for CRM, and legacy setups use a pixel of type CRM.
They wait in a queue, up to a limit. Make's pricing FAQ says scenarios stop until credits are added, and incoming webhooks queue up to your plan's webhook queue size. That is 667 per 10,000 credits, to a maximum of 10,000. With HelloConversions, a busy month of events doesn't move the price, which follows your GHL contacts.
This page is written by HelloConversions. Facts about Make (DIY scenarios) 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