LogoLogo
Back to studio
  • Formsort documentation
  • โฉQuickstart
    • ๐ŸŸขGet started with Formsort
    • ๐ŸŽCore concepts
    • โ„น๏ธQuestion and content reference
    • ๐Ÿ“•Key terms
    • ๐Ÿž๏ธCreate your first flow
    • ๐Ÿ“–Add content and collect answers
      • ๐ŸคณCapture demographic data
      • โ„น๏ธAdd informational content
      • ๐Ÿ” Review your variable schema
    • ๐ŸŽจCreate a theme
      • Set brand guidelines
    • ๐ŸคนPersonalize your flow
      • ๐ŸŒŸTemplate your variables
      • ๐Ÿง Add conditional logic
      • ๐Ÿ’ซUsing conditional logic with Calculated and API variables
      • ๐Ÿ”šEnd the flow
    • ๐Ÿ”€Set up integrations
    • ๐Ÿš€Go live
      • Auditing your flow for content, functionality, and design
    • ๐Ÿ’ผCommon use cases
      • ๐Ÿ’”Disqualify responders
      • ๐Ÿ—“๏ธAdd a scheduling option
      • ๐Ÿ“„Allow responders to read and accept your company policies
  • ๐Ÿ—๏ธBuilding flows
    • Flows and variants
      • Flow starts
    • Adding content
      • Groups
      • Steps
        • Settings
        • Logic
        • Style
      • Questions
        • General Settings
        • Style
        • Address
        • Comparison
        • Confirmation
        • Date
        • Date & Time
        • Email address
        • File upload
        • Grid choice
        • Iframe
        • Image upload
        • Number
        • Payment
        • Phone number
        • Postal code
        • Question group
        • Region
        • Select
          • Providing choices via API or calculation
        • Signature
        • SSN
        • Text questions
        • Yes/No
      • Content
        • General Settings
        • Statement
        • Image
        • Video
        • Next button
        • Divider
        • Map
      • Endings
      • Using markdown
      • Using variable templating
        • Template formatting functions
      • Copy-pasting form content
      • Content library
    • Conditions and logic
      • Logical operator reference
      • Advanced logic
    • Variables (answers)
      • Variables from questions
      • Externally provided variables
      • Calculated variables
      • API lookups
      • System Library variables
      • Orphaned variables
    • Schemas
      • JSON Schemas
      • Validating flow schemas
    • Redirects
    • Styling and themes
      • CSS Reference
      • Overriding theme styling
      • Custom CSS overrides
      • Content area
      • Animations and transitions
      • Form Layout
      • Typography
        • Adobe Fonts
        • Hosting custom fonts
      • Color variables
      • Dimension variables
      • Question containers
      • Assets
      • Form Buttons
        • Select buttons
      • Inputs and dropdowns
      • Checkmarks
      • Tables
      • Sliders
      • Divider lines
      • Progress bar
      • Comparison cards
    • Variant settings
      • Form behavior for returning responders
      • Group ranking API
    • Publishing and versions
      • Preview window
      • Deploying
      • History
  • ๐Ÿ’พHandling data
    • Philosophy and data retention policy
    • Viewing form answers
    • Responder UUIDs
    • Environments
      • Loading different environments
    • Passing data in
      • URL parameters
      • POST body
      • Embed query parameters
    • Custom validators
    • Form answers and events
      • Analytics events
      • Signed requests
      • Event payload shape
      • Submission frequencies
      • Runtime error reporting
      • Admin API
      • Flow content data format
    • Integration reference
      • Amplitude
        • Amplitude cross domain tracking
      • BigQuery
      • FullStory
      • Google Analytics
        • Updating from Universal Analytics to GA4
      • Google Cloud Storage
      • Google Sheets
      • Google Tag Manager (GTM)
        • JavaScript triggered by flow events
      • Hubspot
      • Jornaya
      • Optimizely
      • PostgreSQL
      • Redshift
      • Rudderstack
      • S3
      • Salesforce
      • Segment
        • Segment Setup
        • Segment cross domain tracking
      • Stripe
      • TrustedForm
      • Webhooks
        • Zapier
  • ๐Ÿ“บGoing live
    • Custom domains
    • Built-in analytics
    • Embedding
      • Web-Embed API
        • React-embed
      • Adding authentication
      • Embedding forms in iOS and Android
      • Setting up a dev environment
    • Split testing
    • Preflight checklist
  • ๐ŸขTeams
    • Accounts
      • Roles and permissions
    • Events subscriptions
    • Workspace domain detection
Powered by GitBook
On this page
  • Step 1: Add a Source
  • Step 2: Connect to Source
  • Step 4: Configuring data transmission to Segment within Formsort

Was this helpful?

  1. Handling data
  2. Integration reference
  3. Segment

Segment Setup

This page covers setting up the Formsort -> Segment integration

PreviousSegmentNextSegment cross domain tracking

Last updated 10 months ago

Was this helpful?

Step 1: Add a Source

Choose add a source.

Select "Javascript/Website" and click "Next".

Step 2: Connect to Source

The "Website Name" can be anything, however it is best practice to ensure it will easily identify the source connected.

Copy just the "write key" from the Segment code snippet...

...and paste it into the "Segment Write Key" section of the Formsort Segment integration tab.

The Segment Write Key can also be found in another location in Segment: Sources -> Settings -> API Keys -> Write Key.

Follow Segment's directions to test that Segment is detecting data from your Source, to ensure the URL has been input correctly. When finished, click "done".

Step 4: Configuring data transmission to Segment within Formsort

Send answers

Payload Shape

Append step ID to StepLoaded and StepCompleted event names

When enabled, current Step ID will be included in the step title, e.g. StepCompleted_email.

If no Step ID is defined, it will default to Step Index.

This is not recommended, as the Step ID is by default included in the payload body.

Identification

Custom Domain Proxy

This is likely uncommon, but if you use a custom domain proxy, set the URL here.

Hide IP

If toggled on, the responder's IP will be set to 0.0.0.0 on every request.

Hide Page Fields

If set, path, referrer, url, and search will be excluded from the event page context.

Preview Event Type

This window allows you to view what a payload will look like at different events. In the example above, a StepCompleted event is being previewed.

Create a name in the "Website Name" field and enter the URL of your in the "Website URL" box.

By default, are not enabled and must be toggled on.

Analytic Events are a way to track information about the flow, and the answers given by the user. By toggling on "enabled events", Formsort will send the information collected from users at specific times, based on your selection. For more context, please see our reference for Analytics Events .

Please refer to our section .

Please refer to our section .

Please refer to our section .

๐Ÿ’พ
deployed form
Analytic Events
here
Shape of Payloads
Sending form answers data to Segment
How Formsort uses identify()
Be sure to leave the quotation marks off
The payload preview for StepCompleted