Connect Unbounce & set up form-submission tracking

Unbounce form submissions hit FunnelTrack via webhooks. FunnelTrack matches each submission to the visitor's pre-submission ad session using the FunnelTrack pixel plus IP + user-agent fingerprinting, then routes the conversion to Meta, Google Ads, GA4, TikTok, and any other connected destination — each with a deduplication-grade event ID so your platform-side reporting stays clean.

In Unbounce, open Script Manager and add your FunnelTrack pixel snippet. Use these settings:

• •Placement — Head
• •Included on — All pages

Webhook setup in Unbounce is per-page. From the Unbounce pages list, open the landing page that contains the form you want to track. You'll repeat this step for every page with a form.

On the page's overview, open the Webhooks tab and paste the FunnelTrack webhook URL from Integrations → Sources → Unbounce. Set the request format to JSON.

The URL follows this format:

https://app.funneltrack.com/api/webhook/unbounce/{workspace_id}

Unbounce ships two sets of fields in the webhook payload by default: Page Data (auto-populated by Unbounce) and Form Data (the fields your visitor filled out). FunnelTrack reads both by their default names, so the mapping section on the Unbounce side should be left as-is.

By default Unbounce ships page_uuid as the form identifier, which is functional but not human-readable. Adding a hidden custom field on the Unbounce form called form_id with a friendly value (e.g. webinar_lead or contact_us) lets you reference that name as a custom event parameter or filter condition inside FunnelTrack.

In FunnelTrack, open a connected destination's routing page (e.g. Unbounce → Meta Conversions API). Either use the All Form Submissions template for broad coverage, or add a per-form custom event. Then:

• •Submit a test form so FT has a payload to discover
• •Click Add Event
• •Click Find Last Submission to pull the discovered field schema
• •Assign an event name (this is what shows in the integration's event summary and on the outbound dispatch)

Two kinds of parameters can be mapped on the event:

• •Event Parameters — static values you type in (e.g. currency: USD) or dynamic values mapped from form fields (e.g. value from a budget field). These ship to the destination as standard or custom event parameters.
• •User Data Parameters — FunnelTrack auto-captures email, phone, name, address, etc. from the standard fields. If your form collects identifiable info for multiple people (e.g. a referral form with both referrer and referee emails), use this section to manually map which field is the primary contact. Otherwise FT picks the first found contact value automatically.

Use the Conditions section to fire the event only when the submission matches certain criteria. A common Unbounce pattern is gating on variant to split A/B-test conversions into separate reporting events — e.g. only fire the event when variant equals a.

Save the event card. Submit a final test entry on the form — the saved card on the routing page summarizes the event as configured, the inbound usage log row reads Form Submission, and the outbound log row reads the destination event name you assigned.

• •Unbounce webhook setup is per-page.If you have a form on 5 landing pages, configure 5 webhooks. Same FunnelTrack URL, just paste it into each page's Webhooks tab.
• •The FT pixel must be deployed via Script Manager. Set Placement to Head and Included on to All. Without the pixel, FT still receives the webhook but can't stitch it to the visitor's pre-submission browsing — match quality drops materially.
• •page_uuid is the discriminator FT uses to identify forms. Unbounce doesn't have form-level IDs like Gravity Forms or Jotform — every form is "the form on this page." Add a custom form_id hidden field if you want human-readable identification.
• •A/B variants on the same page share a page_uuid but differ on variant. Use Conditions (variant equals a) to route variants to different conversion events.
• •One webhook URL, every page.Your workspace has a single FunnelTrack webhook URL — paste the same URL into every Unbounce page's Webhooks tab. FT routes based on page_uuid (and optional form_id) inside the payload.

Unbounce ships one event type through its webhooks: a form submission. FunnelTrack receives the full payload and discovers every field on the form, so you can map any of them to event parameters or user data on the destination side.

There's no fixed event catalog here — each page's submission is the event, and page_uuid (plus an optional custom form_id) is the discriminator FunnelTrack uses to route it to the right destination config.

• •Lead-gen page → Meta Lead. A single form with standard email + phone mapping fires Meta Leadserver-side. This is the highest-volume use case and recovers the conversions Meta's client-side pixel was losing.
• •Multi-page webinar funnel → GA4 generate_lead + Google Ads conversion. Same webhook, two destinations, separate event cards each with the page's page_uuid baked into the trigger.
• •A/B test routing → split variants to different reporting events. Use the Conditions section to filter on variant so variant A and variant B fire distinct conversion events for clean comparison reporting.