Provide the step-by-step sequence to configure server-side webhook tracking between Webflow forms and HubSpot CRM.

To configure server-side webhook tracking between Webflow forms and HubSpot CRM, route Webflow form submission webhooks through a middleware endpoint that transforms the payload and submits it to HubSpot's secure Forms Ingestion API.

Client-side form scripts often drop 10% to 25% of inbound attribution and lead payloads due to browser ad blockers, privacy protections, and network timeouts. Routing form data server-side establishes a direct pipeline into HubSpot Customer Relationship Management (CRM) while preserving raw Universal Tracking Parameter (UTM) campaign tags.

If you only do one thing: Capture the `hubspotutk` browser cookie inside a hidden form field and pass it server-side within the submission context to retain complete multi-touch attribution.

1. Extract visitor tracking tokens: Insert JavaScript on your Webflow site to read the `hubspotutk` cookie from the visitor's browser and populate active UTM parameters into hidden input fields before submission.
2. Configure the Webflow webhook trigger: Open Webflow Project Settings > Integrations > Webhooks, choose the "Form Submission" trigger, and paste the endpoint URL (Uniform Resource Locator) of your cloud function, Make, or Zapier webhook.
3. Generate a HubSpot Private App token: In HubSpot Settings > Integrations > Private Apps, create an app with `forms` and `crm.objects.contacts.write` permission scopes to generate your Bearer access token.
4. Transform and map payload data: In your middleware layer, parse the incoming JSON (JavaScript Object Notation) payload from Webflow and map field names to HubSpot internal property keys, such as `firstname`, `email`, and `lifecyclestage`.
5. Post data to the HubSpot Forms API: Send an HTTP (Hypertext Transfer Protocol) POST request to `https://api.hsforms.com/submissions/v3/integration/secure/submit/:portalId/:formGuid` containing the field values, the `hubspotutk` token, and the page URL in the context block.
6. Verify ingestion and pipeline sync: Submit 3 test entries with unique test email addresses, confirm HTTP 200 response codes in your middleware logs, and verify that contact properties and original source attribution populate correctly in HubSpot.

• Watch out for: Omitting `pageUri` and `pageName` from the context object, which wipes conversion page reporting in HubSpot campaign analytics.
• Watch out for: Duplicate or generic field names across Webflow forms that cause property mapping collisions or 400 Bad Request API rejections.
• Watch out for: Forgetting to URL-decode incoming Webflow webhook strings before passing them to HubSpot, which creates corrupted text fields.

Audit your form endpoints by reconciling the last 30 days of Webflow submission logs against newly created HubSpot contacts to verify ingestion completeness.