CRM connector data paths

Where WordPress CRM plugins send visitor data

A CRM plugin can collect contacts from a form. Some also load a tracking script on every page, including visits where no form is submitted. Requests to that service include an IP address and browser information. Other CRMs keep contacts on your WordPress server without a site-wide tracking script. This table describes the setups below; your settings can change where requests go.

Based on plugin documentation, not tests of your site. Your settings can change what loads. This is not legal advice or a compliance rating.

Scan your site for third-party requests

How we group CRM plugins

We compare the CRM setups named below. A plugin that stores contacts on your server without a site-wide tracking script is different from a plugin that loads an outside CRM tracking script on every page. A form that only posts to an outside CRM on submit is a different setup from site-wide tracking. We have not tested consent timing or how long CRM logs are kept.

CRM plugins

No paid placement. Contacts stored on your site first, then outside CRM services, then plugins not yet reviewed. Names are alphabetical within each group.

PluginDocumented behaviorDocumented service domainsHow long data is keptBefore consentLinksSource
FluentCRM

This row covers FluentCRM when contacts, tags, and campaigns stay in WordPress. The listing describes it as self-hosted with no required outside CRM connection. Optional integrations that send contacts to another service are a different setup and are not this row. Consent timing is not tested here.

Contacts stored on your siteNo outside CRM tracking script documented for this setup. Other page requests are not covered.Not assessedNot tested
  • None
Jetpack CRM

This row covers Jetpack CRM, also listed as zero-bs-crm, when contacts, invoices, and quotes stay in WordPress. Optional Jetpack or WooCommerce extras are a different setup and are not this row. Consent timing is not tested here.

Contacts stored on your siteNo outside CRM tracking script documented for this setup. Other page requests are not covered.Not assessedNot tested
  • None
ActiveCampaign

This row covers ActiveCampaign Subscription Forms when site tracking is enabled. The page loads a tracking script from diffuser-cdn.app-us1.com. Embedded forms without site tracking are a different setup and belong with form plugins. Consent timing is not tested here.

Outside CRM servicediffuser-cdn.app-us1.comNot assessedNot tested
  • None
Brevo

This row covers the official Brevo plugin, formerly Sendinblue, when marketing automation is on. The page loads a script from cdn.brevo.com. Form-only use without that script, and optional web-push scripts, are different setups and are not this row. Consent timing is not tested here.

Outside CRM servicecdn.brevo.comNot assessedNot tested
  • None
Brilliant Web-to-Lead for Salesforce

This row covers Brilliant Web-to-Lead when the built-in form posts to Salesforce. That is a form submission to an outside CRM, not a site-wide tracking script on every page. Generic form plugins belong on the form plugin privacy page. Consent timing is not tested here.

Outside CRM servicewebto.salesforce.com (Form submission endpoint)Not assessedNot tested
  • None
HubSpot

This row covers the official HubSpot plugin when a portal is connected. The plugin enqueues a site-wide tracking script from js.hs-scripts.com on front-end pages. Forms and live chat are extra embeds and are not this row. Consent timing is not tested here.

Outside CRM servicejs.hs-scripts.comNot assessedNot tested

What this table does and does not prove

This table describes the named CRM setups. It does not show what loads on your site. Where no outside CRM tracking script is documented, that applies only to the setup described. Other page requests are not covered. A form that posts to an outside CRM on submit is not the same as a site-wide tracking script. Plugins marked Not reviewed have not been assessed. We have not tested consent timing, and we have not assessed how long CRM logs are kept. The site scan linked below checks for third-party requests; it does not access your WordPress database.

Documentation snapshot: Oct 1, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-crm-plugin-privacy