LeadConnector

Yes. You need an active LeadConnector account and a connected location to use the CRM-connected features.

The WordPress plugin is free. A LeadConnector subscription may be required to use connected services such as widgets, funnels, forms, calendars, email, and CRM tools.

Open LeadConnector in the WordPress admin menu and follow the connection flow. Settings changes use authenticated WordPress admin requests.

Open LeadConnector > Chat Widget, enable the widget, and select the widget you want to display. The plugin loads the selected LeadConnector chat widget on your WordPress site.

Open LeadConnector > Funnels, choose a funnel and funnel step, set the WordPress slug, and publish it. Funnel pages are stored in WordPress as LeadConnector funnel content and routed through the selected display method.

The plugin includes [leadconnector_form], [leadconnector_calendar], [leadconnector_survey], [leadconnector_quiz], [leadconnector_reviews_widget], and [leadconnector_phone_number_pool]. The historical [lc_*] aliases remain registered for backward compatibility and will be removed in a future major release.

Yes. The plugin includes Elementor-specific compatibility support and frontend styles for supported LeadConnector funnel pages. Compatibility can vary by theme, template, and builder configuration.

Yes. LeadConnector includes Right-to-Left language support for supported plugin screens and frontend output. External Services LeadConnector is a CRM/marketing platform operated by LeadConnector LLC. This WordPress plugin is a thin client for that platform: connecting WordPress to your LeadConnector account, embedding chat widgets, forms, calendars, surveys, quizzes, reviews, and phone-tracking pools, importing and rendering funnel pages, opening the LeadConnector authorization flow, and optionally purging an external CDN cache. Every feature that needs the LeadConnector platform will cause one or more HTTP requests to LeadConnector-owned hosts (and, for form-embed support, a sibling messaging host). This section documents every external host the plugin reaches out to, why, when, what data crosses the wire, and what does not. All LeadConnector-owned hosts (leadconnectorhq.com, msgsndr.com, reputationhub.site subdomains listed below) are governed by the same LeadConnector terms of service and privacy policy: Terms of service: https://www.leadconnectorhq.com/terms2 Privacy policy: https://www.leadconnectorhq.com/privacy-policy Each domain block below repeats the per-domain links so reviewers (and end users) can verify them in place. Calls to these hosts only happen when the corresponding feature is enabled, configured, or used. A feature that is disabled, an empty configuration value, or a shortcode that is not present on the page will not trigger any of these requests. services.leadconnectorhq.com (admin / server-to-server and chat widget browser endpoints) What it is: LeadConnector's authenticated services API. The plugin's primary read/write surface for account and configuration data, OAuth token exchange / refresh, optional CDN cache purge, chat-widget service endpoints, and one allowlisted host for optional funnel tracking-code downloads supplied by LeadConnector during import.

OAuth access token (Authorization: Bearer header) when an admin has connected their account; OAuth refresh token during token-refresh calls only. Connected location ID. Plugin settings being saved (chat widget selection, SMTP enable flag and configuration, SEO override fields, white-label URL, AI Pages flags). Funnel/page identifiers and the WordPress post ID they were imported into (during funnel import, refresh, and native-mode warm-up). Custom-value field keys for the connected location during the admin "sync custom values" action. Cache-purge target identifiers ({locationId}, {wpId}) inside the URL path when CDN purge fires; no request body is sent for cache-purge calls. Chat-widget service URL configuration is exposed to the widget loader through script data-* attributes when the chat widget is enabled. Optional funnel tracking-code download URL when LeadConnector supplies a download URL on this host during import / publish.

OAuth connect / disconnect flow (admin clicks "Connect to LeadConnector" or "Disconnect"). OAuth token refresh (background WP-Cron task leadconnector_oauth_token_refresh_cron, fired only when a connected access token is approaching expiry). Settings save on the LeadConnector admin screen. Funnel browse, import, and refresh actions (admin clicks "Import" / "Refresh" inside the LeadConnector funnels UI). Custom-value listing and sync action. SMTP enable / disable / test send actions. Reviews widget admin browsing. Admin REST proxy requests that target an allowlisted full URL on this host. CDN cache purge (see below for triggers). CDN cache-purge triggers (only when CDN_WP_ID or CDN_SITE_ID is defined in wp-config.php and an active OAuth session exists). The plugin sends an authenticated empty-body POST to services.leadconnectorhq.com/wordpress/lc-plugin/site/{locationId}/{wpId}/clear-cache on: A connected WordPress administrator clicking "Purge everything on all domains" in the admin bar. The LeadConnector settings page being saved. A public post (any post type registered with public => true, including standard post, page, WooCommerce products, and third-party CPTs) being published or updated via WordPress's save_post hook. Auto-saves, revisions, and non-public post types are skipped. Custom-value placeholder fallback (a single front-end-render code path): when a {{custom_values.…}} placeholder is referenced on a public page and the local transient cache is cold for that key, the public renderer falls back to an authenticated read from services.leadconnectorhq.com using the admin-issued OAuth bearer that the site has stored. The fallback is a read-only lookup; no visitor data is forwarded. Visitor browser trigger: when the chat widget is enabled, the browser loads widgets.leadconnectorhq.com/loader.js with data-server-u-r-l and data-marketplace-u-r-l values pointing at services.leadconnectorhq.com; the widget may contact those service endpoints directly. Browser requests include the selected widget configuration plus normal browser metadata (IP address, User-Agent, Referer, language headers, and any cookies the host previously set). What is not sent by PHP server-to-server calls: WordPress administrator credentials, password hashes, WordPress secret keys/salts, WordPress authentication cookies, other plugins' data, visitor IP, visitor User-Agent, or visitor referrer. Chat-widget browser requests are initiated by the visitor's browser and carry normal browser metadata as described above. Service: provided by LeadConnector LLC. Service terms: https://www.leadconnectorhq.com/terms2 Privacy policy: https://www.leadconnectorhq.com/privacy-policy rest.leadconnectorhq.com (admin / server-to-server) What it is: LeadConnector's REST API. Used by legacy admin flows that have not yet migrated to services.leadconnectorhq.com and as one allowlisted host for optional funnel tracking-code downloads supplied by LeadConnector during import. What is sent: the LeadConnector API key (when API-key auth is configured instead of OAuth), location ID, page/funnel IDs, custom-value keys, and request parameters required by the admin action. For optional tracking-code downloads, WordPress sends a server-side GET to the LeadConnector-supplied download URL. When sent: admin-triggered actions only - account validation against the REST API, certain custom-value reads, certain legacy data pulls, admin REST proxy requests that target an allowlisted full URL on this host, and funnel import / publish when the supplied tracking download URL points to this host. The plugin never calls this host from the public render path.