

The mapping screen of a form: one card per HubSpot object ("#1 Contact", "#2 Deal"), each with its own field mapping, the association with the object above it, and the Sync switch with Save Changes at the top.
Sends each Contact Form 7 submission to HubSpot. Your forms stay as they are.
One form can create several linked records. A quote request, for example, can create a contact, their company and a deal in the pipeline and stage you choose. A support form can open a ticket. You can also send a form to an existing HubSpot form, so HubSpot workflows and page tracking treat it like a HubSpot form.
This plugin sends Contact Form 7 submissions to HubSpot, a third-party service, when a form is submitted and synced. It sends the values of the mapped form fields, uploaded files that are mapped, and, when enabled, attribution values; for HubSpot form targets it also sends the visitor’s IP address, the HubSpot tracking cookie and the page the form was sent from. In the admin it reads your HubSpot properties, forms, pipelines and subscription types to fill the mapping screens.
The plugin sends requests to:
HubSpot Terms of Service: https://legal.hubspot.com/terms-of-service
HubSpot Privacy Policy: https://legal.hubspot.com/privacy-policy
Attribution cookies are off by default. When you turn on “Attribution cookies” in the plugin settings, the site stores the campaign parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content) and ad click ids (gclid, fbclid) of the visitor’s landing page in first-party cookies named cf7hs_* for up to 30 days (some browsers shorten this). When a consent plugin supports the WP Consent API, the cookies are set only after marketing consent. The values are sent to HubSpot with a contact form the visitor submits. Marketing cookies may need visitor consent where the law requires it.