Name: HITJMS Integration
Author: hitjms

HITJMS Integration connects your WordPress site to the HITJMS behavioral health platform API. It lets treatment centers and medical organizations capture intake leads, sync contacts, inject tracking, and embed a chat widget — all configured from a single settings screen.

Features

Intake form — a built-in lead form (or a HITJMS-native form by ID) that submits securely to the HITJMS API via AJAX, with a GA4 hitjms_lead_submitted event.
Contact sync — pull your HITJMS patient/contact records into a local table on a schedule (hourly / twice daily / daily) via WP-Cron, or on demand.
Auto-blogging — automatically mirror the AI-generated blog posts from your HITJMS site into WordPress by polling your site’s RSS feed. Import as drafts or published, assign author and category, and optionally download featured images. Posts are de-duplicated so nothing is imported twice.
Tracking — enter your HITJMS site ID (hjpx_…) plus, optionally, a Google Tag Manager (GTM-XXXXXXX) or Google Analytics 4 (G-XXXXXXXXXX) ID; the plugin builds and loads the correct tags for you. You never paste a script.
Chat widget — drop in your HITJMS chat embed site-wide or inline via shortcode.
Embed codes — copy-and-paste HTML for the chat widget, intake form and tracking pixel, for pages this plugin does not run on (a landing page, an old site, a page builder that strips shortcodes).
Shortcodes — [hitjms_intake_form], [hitjms_chat_widget], [hitjms_contact_list], [hitjms_lead_count] and more.

Requires a HITJMS account. You provide your own API key from the HITJMS Developer dashboard. Without a key the plugin stays inactive/idle. If you do not have an account yet, see hitjms.com for plans and pricing.

All connections to third-party services are described in the “External services” section below. Nothing is sent anywhere until you enter your API key or enable a feature — the plugin makes no outbound requests in its default state.

HIPAA / PHI note: Intake and contact data may constitute Protected Health Information (PHI). Use of the HITJMS service for PHI requires a signed Business Associate Agreement (BAA) with HITJMS — read more about our HIPAA posture. The plugin never writes contact data to logs or browser storage, and the contact list is restricted to users with the edit_posts capability.

See it in action

A walkthrough of the HITJMS dashboard this plugin connects to — leads, intake, tracking and content in one place:

Five organic growth moves for filling your calendar without ad spend — the marketing thinking behind the auto-blogging and tracking features:

What clinical directors actually need from marketing, and why most agencies miss it:

More on the HITJMS YouTube channel and the HITJMS blog.

Who it is for

Built for behavioral health and senior care organizations: mental health centers, addiction treatment centers, detox facilities, IOP and PHP programs, sober living homes and hospice providers.

External services

This plugin connects to the following external services. Each one is described below with the data it receives, when that happens, and links to its terms and privacy policy.

1. HITJMS platform API (api.hitjms.com)

This is the service the plugin is a client for. It is required for the plugin’s core functionality, and you must have your own HITJMS account and API key.

What it is used for: creating intake submissions in, and reading contact records from, your HITJMS account.
What is sent and when: when a visitor submits the intake form, the values they enter (such as name, email, phone, insurance provider, referral source and notes), together with your site’s URL, are sent over HTTPS to https://api.hitjms.com/api/v1/intake. When Contact Sync runs (on the schedule you choose, or when you click “Sync Now”), the plugin sends your API key to https://api.hitjms.com/api/v1/patients and stores the returned contact records in your site’s database for display to logged-in staff only. When you click “Test Connection”, your API key alone is sent to verify it. No data is sent unless you have saved an API key.
Service provider: HITJMS.
Terms of Service: https://hitjms.com/terms
Privacy Policy: https://hitjms.com/privacy

1b. HITJMS visitor tracking pixel (api.hitjms.com) — optional

What it is used for: recording visits, traffic sources and form conversions for your site in your HITJMS dashboard.
What is sent and when: nothing by default. Only when you enter your HITJMS site ID on the Tracking tab and switch the pixel on does the plugin load https://api.hitjms.com/js/tracker.js on your public pages. Visitors’ browsers then send HITJMS the page URL, referrer, traffic-source parameters, IP address and user agent. No cookies are set. Clearing the site ID or switching the pixel off stops all of it.
Service provider: HITJMS.
Terms of Service: https://hitjms.com/terms
Privacy Policy: https://hitjms.com/privacy

2. Your HITJMS site’s RSS feed (Auto-Blog only)

What it is used for: importing blog posts published on your HITJMS site into WordPress.
What is sent and when: only when you enable Auto-Blogging and supply a feed URL. On the schedule you choose (or when you click “Import Now”) your server requests that feed URL — a normal HTTP GET containing no personal data. If “Featured Images” is enabled, images referenced by the feed are downloaded to your Media Library.
Service provider: HITJMS (the same account and policies as above).
Terms of Service: https://hitjms.com/terms
Privacy Policy: https://hitjms.com/privacy

3. Google Tag Manager (googletagmanager.com) — optional

What it is used for: loading the tag container you configure, so you can manage marketing and analytics tags without editing your site.
What is sent and when: nothing by default. Only when you enter a GTM container ID on the Tracking tab does the plugin load https://www.googletagmanager.com/gtm.js on your public pages. Visitors’ browsers then send Google the usual request data — IP address, user agent, referring URL and the page being viewed — plus whatever the tags inside your container are configured to collect. A <noscript> fallback to https://www.googletagmanager.com/ns.html is included for browsers without JavaScript. Removing the ID stops all of it.
Service provider: Google.
Terms of Service: https://marketingplatform.google.com/about/analytics/tag-manager/use-policy/
Privacy Policy: https://policies.google.com/privacy

4. Google Analytics 4 (googletagmanager.com) — optional

What it is used for: measuring page views and traffic sources for your site, and recording a hitjms_lead_submitted event when an intake form is submitted.
What is sent and when: nothing by default. Only when you enter a GA4 measurement ID on the Tracking tab does the plugin load https://www.googletagmanager.com/gtag/js on your public pages. Visitors’ browsers then send Google page view events including the page URL, referrer, IP address, user agent and the Google Analytics client identifier stored in a cookie. Removing the ID stops all of it.
Service provider: Google.
Terms of Service: https://marketingplatform.google.com/about/analytics/terms/us/
Privacy Policy: https://policies.google.com/privacy

5. HITJMS chat widget (api.hitjms.com) — optional

What it is used for: displaying the HITJMS live chat widget on your site.
What is sent and when: nothing by default. Only when you enter your HITJMS site ID on the Chat Widget tab and either enable the widget site-wide or place the [hitjms_chat_widget] shortcode does the plugin load https://api.hitjms.com/js/chatbot-widget.js on your public pages. HITJMS then receives visitors’ IP address, user agent and page URL, plus anything they type into the chat. Because that happens before the visitor types anything, the widget waits for consent on sites running a consent plugin (see below). Clearing the site ID stops all of it.
Service provider: HITJMS.
Terms of Service: https://hitjms.com/terms
Privacy Policy: https://hitjms.com/privacy

Visitor consent: every third-party service above is off unless you configure it. When a consent plugin implementing the WP Consent API is active, the plugin waits for the visitor’s decision before loading anything third-party:

The HITJMS visitor pixel, Google Tag Manager and Google Analytics require the statistics category.
The chat widget requires the marketing category, where consent platforms usually place third-party embeds. If your consent policy treats live chat as a necessary service instead, change the category with the hitjms_chat_consent_category filter (for example to functional).

Sites with no consent plugin installed are unaffected — everything loads as configured.

Two filters let you switch these off per page, which is recommended for any page that collects health information: hitjms_allow_tracking for the visitor pixel and Google tags, and hitjms_allow_chat for the chat widget.