Connect HighLevel & set up workflow tracking

FunnelTrack captures HighLevel form submissions, orders, appointments, opportunities, and pipeline events server-side via HighLevel Workflows — each event you want to track is a Workflow with a Webhook action pointing at FunnelTrack. We stitch every event back to the visitor's ad session through the FunnelTrack pixel, so the conversion you fire to Meta, Google, TikTok, and the rest carries the original click ID, identity data, and session context.

From the Pixel section of FunnelTrack, copy your pixel snippet and deploy it on every page of your site, plus any third-party landing pages that feed traffic into HighLevel.

In HighLevel, the pixel needs to be installed per asset — each funnel, website, and store separately. Open the asset and go to Settings → Tracking Code (called Head Tracking Code on some assets), paste the FunnelTrack pixel snippet, and save.

In FunnelTrack, open Integrations → Sources → HighLevel and copy the Webhook URL shown on the connection page. This is the single endpoint every HighLevel workflow will post to.

FunnelTrack supports these HighLevel events out of the box. Each one gets its own workflow in HighLevel and its own template card on the destination routing page in FunnelTrack:

In HighLevel, go to Automation → Workflows → Create Workflow for each event you want FunnelTrack to receive. Workflow construction is the same shape every time:

1. Pick the triggerfor the event you're tracking. For a Form Submission event, the trigger is Form Submitted; for an Appointment Booked event, it's Customer Booked Appointment; and so on.
2. Add a Webhook action as the next step in the workflow.
3. Paste the FunnelTrack HighLevel webhook URL (from step 2) into the action's URL field.
4. Add the event custom data keyon the webhook action — see step 5 for the value to use. This is how FunnelTrack knows which event type each payload is (HighLevel doesn't include the event type in the payload by default).
5. Save and publish the workflow.

On each workflow's Webhook action, add a Custom Data entry with key eventand the exact value from this table. The value tells FunnelTrack which event type the payload represents — without it, the event won't match a template card on the destination side.

Open a connected destination's routing page — e.g. HighLevel → Meta Conversions API. You'll see one template card per supported HighLevel event, grouped into Forms, Orders, Pipeline, and Opportunity sections. Toggle on the ones you want, pick the destination event for each (Meta's Lead / Purchase, a Google Ads conversion action, etc.), and save.

You can also click Add Event to create a custom card alongside the templates — useful when you want one HighLevel event to fire as different destination events under different conditions (e.g. lead-quality scoring, funnel-specific routing). The Add Event modal includes an Event Name field so per-workflow / per-funnel cards can be named distinctly in the routing list and usage logs.

Click + Add Parameters on a card to send additional fields to the destination. Parameters can be static (you type the value) or dynamic (pulled from the HighLevel payload via the field picker). Read more about using event parameters in FunnelTrack.

Every HighLevel workflow payload carries the same envelope (contact + attribution + workflow + customData), and event-specific fields for orders / opportunities / appointments. The full set of FunnelTrack-mappable payload fields:

Use the Conditions section to gate the dispatch behind one or more rules on the HighLevel payload. Read more about using conditions in FunnelTrack. A few patterns customers run a lot:

• •Workflow-scoped lead events — fire only when workflow.name equals "Discovery Call Form" so each lead-gen workflow gets its own attribution rather than sharing one generic Form Submission event.
• •Pipeline-stage milestones — fire on Pipeline Stage Changed only when pipleline_stage equals "Demo Scheduled" (yes, HighLevel ships that field with the misspelling).
• •High-value order split — split Order Submitted into two cards, one with order.total_price > 500 firing a custom HighValuePurchase event, the other firing Purchase.

Trigger a real test on the underlying funnel / store / calendar that your workflow fires from. Within a few seconds you should see an inbound row in the usage log labeled with the HighLevel event name (e.g. Form Submission, Order Submitted), followed by one outbound row per connected destination — each delivered to the destination event you mapped to.

• •One workflow per event type. Build a separate HighLevel workflow for every event you want to track — each uses its own Trigger and its own customData.event value on the Webhook action. This is what HighLevel meters as executions, so the Workflow Pro tier you pick should reflect your expected monthly volume across all FunnelTrack workflows.
• •customData.event is the routing key.The whole integration hinges on this single value. Set it once per workflow, use the exact strings from the table in step 5, and FunnelTrack's template cards do the rest.
• •Pixel install is per-funnel / website / store. HighLevel doesn't expose a sub-account-wide head code, so each asset needs the pixel added individually under Tracking Code / Head Tracking Code. New assets need the pixel installed at launch.
• •One FunnelTrack webhook URL, every workflow. Reuse the same URL across all workflows on the sub-account — FunnelTrack uses customData.event to route each payload to the right template card.

• •Discovery form → Meta Lead.One HighLevel workflow on the discovery form's Form Submitted trigger with customData.event = form_submission. In FunnelTrack, the Form Submission template card on HighLevel → Meta routes it as a Meta Lead. Add a Funnel-Name condition for per-funnel attribution.
• •Order Submitted → Meta + Google Ads Purchase. One HighLevel workflow on Order Submitted with customData.event = order_submitted. Two destination cards: Meta Purchase and Google Ads purchase conversion action, both reading order.total_price as the value.
• •Opportunity Won → Meta CompletePayment + GA4. A separate workflow on the Opportunity Status Changed → Won trigger with customData.event = opportunity_won. Useful for high-touch sales pipelines where the winnable signal is a manual stage update, not an order form.