User Data Parameters

A) Auto-extraction from source events

Form sources (Gravity Forms, Jotform, Unbounce, HighLevel, ClickFunnels 2.0) auto-detect email, phone, first_name, last_name, full_name (auto-split into first + last), and address fields using two passes:

• •Exact field-name match — e.g. Unbounce maps email, phone / telephone, first_name, last_name, name (auto-split on first space), city, state / province, country, zip_code.
• •Value-pattern fallback — any field with an email-shaped value auto-maps to email; any 10–20 digit phone-shaped value auto-maps to phone. Catches custom field names like contact_email or mobile_number.
• •Calendly — pulls email, name, and phone (from text_reminder_number) from the standard payload paths.
• •HighLevel — pulls from top-level fields plus order.customer.* paths for purchase events.

B) Auto-capture from the FunnelTrack pixel

• •IP address — IPv6-preferred (via api64.ipify.org) with an IPv4 fallback that's used to match webhook-only sources back to a pixel session.
• •User agent — captured from the browser on every pageview.
• •Click IDs — fbclid (auto-formatted and persisted as _fbc per Meta's spec), gclid, wbraid, gbraid, ttclid, rdt_cid, msclkid, sccid (Snapchat), oppref, li_fat_id.
• •Platform first-party cookies — _fbc, _fbp, _gcl_aw, _gcl_gb, _gcl_gs, _ttp, _epik, li_fat_id.
• •GA4 client_id and session_id — parsed from the _ga cookie (client_id) and every _ga_<container> cookie (per-container session_id).
• •All 9 UTM parameters — utm_source, utm_medium, utm_campaign, utm_content, utm_term, utm_id, utm_source_platform, utm_marketing_tactic, utm_creative_format.

C) Identity-resolution waterfall

When a webhook event fires for a contact who doesn't arrive with a pixel session attached, FunnelTrack runs a multi-tier identity matcher to stitch them to the right visitor session — and therefore the right UTMs, click IDs, and platform cookies. The waterfall runs in this order, stopping at the first match:

1. Direct session ID — when the source ships a pre-known pixel session ID (e.g. a hidden form field). 1:1 match, confidence 1.0.
2. GA4 client_id direct match— when the source ships the visitor's GA4 client_id (HighLevel does this on every workflow webhook), match it against sessions.ga_client_id. 30-day lookback. Near-deterministic.
3. Contact history match — match by email_hash or phone_hash against previously stitched contacts. Catches returning visitors and duplicate contact records.
4. Fingerprint match — SHA-256(IPv4 | user_agent) against pixel sessions that store the same hash. 2-hour window.
5. IP-only match — raw IPv4 match for sources without a user agent (Jotform). 30-min lookback, falls back to a tighter 2-min window when ambiguous.
6. Time-proximity match — if exactly one unresolved session was active in the last 60 seconds when the webhook arrives, link to it.

Once a match is found, the contact's full PII snapshot is attached to the event and forwarded into the dispatcher.

D) Hashing

• •Hashed (SHA-256) before dispatch — email, phone, first_name, last_name, city, state, zip, country, date_of_birth, gender, and external_id are hashed before being sent to Meta CAPI, Google Ads, TikTok, Snapchat, Reddit, Pinterest, OpenAI, LinkedIn, and Microsoft Ads.
• •Sent plaintext(per each platform's spec) — IP, user agent, fbc, fbp, gclid, and other click IDs.
• •Normalization runs before hashing— phone is digits-only (country code included, no +), email is lowercased + trimmed, state is reduced to the 2-char ANSI abbreviation, country to a 2-letter ISO 3166-1 alpha-2 code, and so on per each platform's rules.
• •Field-name translation per destination — Meta wants em / ph / fn / ln; GA4 wants sha256_email_address / sha256_phone_number; Google Ads wants emailAddress / phoneNumber (already hashed). FunnelTrack handles every translation automatically.

1. Your form collects identifiable info for multiple people. A B2B form with both "Your Email" and "Decision Maker Email" — auto-detection picks the first email-typed field it finds. If you want the decision maker's email going to your ad platforms instead, manually pick the right source field in User Data.
2. Field names that don't match auto-detection AND values that aren't email/phone shaped. Rare, but it happens. Example: a custom CRM ships a subscriber_id field that should go to ad platforms as external_id(Meta's stable customer ID for cross-session matching). Map it manually.
3. You want to send city / state / zip but the form only has a combined address field. Map the combined field to whichever canonical destination makes sense, or pre-split it on your form side before submission.
4. Sending an external_id for cross-event matching (e.g. Stripe customer ID, your CRM contact ID, an auth user ID). Meta and Google use external_id heavily for Advanced Matching — adding it lifts match quality on returning buyers significantly.

Canonical fields FunnelTrack accepts

Where to map

On any source → destination event card, expand the User Data section, click Add Mapping, pick the canonical field on the left (e.g. email), and pick the source field on the right (e.g. customData.decision_maker_email). Save the card and the mapping ships on every future event from that source-destination pair.