The Clixx CRM plugin connects your WordPress site to your Clixx CRM account so you can insert lead capture forms from your campaigns into any page or post using:<\/p>\n\n
[clixxcrm_formulario hash=\"...\"]<\/code><\/li>\n- Gutenberg block: \"Clixx CRM Form\"<\/li>\n
- Standalone HTML embed snippet (with built-in style customizer)<\/li>\n<\/ul>\n\n
The connection is established by entering the email of your Clixx CRM account and the API token generated inside the CRM. The token is validated server-side against the company associated with it; if the email does not belong to that company, or the company does not have an active subscription, the connection is refused.<\/p>\n\n
Submissions are sent directly from the visitor's browser to your Clixx CRM. The plugin does not store any visitor data on your WordPress site.<\/p>\n\n
External services<\/h3>\n\n
This plugin connects to the Clixx CRM SaaS (https:\/\/app.clixx.com.br), which is the service the plugin exists to integrate with. The connection happens in three situations:<\/p>\n\n
\nConnecting your account (admin only).<\/strong> When you submit your email and API token on the \"Clixx CRM > Connection\" screen, the plugin sends a POST request from your server to https:\/\/app.clixx.com.br\/api\/auth\/verify<\/code> containing your email and the API token. This is required to validate the token, identify your company in the CRM and confirm the subscription is active.<\/p><\/li>\nListing your forms (admin only).<\/strong> When you open the \"Clixx CRM > Forms\" screen, the plugin sends a GET request from your server to https:\/\/app.clixx.com.br\/api\/anuncios<\/code> using your API token. The response (list of your campaigns \/ forms) is cached for 5 minutes in a WordPress transient. No visitor data is involved.<\/p><\/li>\nForm submissions from visitors (front-end).<\/strong> The shortcode [clixxcrm_formulario]<\/code> renders an iframe pointing to https:\/\/app.clixx.com.br\/inscricao\/{hash}<\/code>, and the standalone \"Embed HTML\" snippet contains JavaScript that, on submit, sends the visitor-typed form fields (name, e-mail, phone, plus any custom fields you configured in the CRM, and any UTM parameters present in the URL) via fetch()<\/code> directly from the visitor's browser to https:\/\/app.clixx.com.br\/api\/webhook\/inscricao\/{hash}<\/code>. The plugin does NOT store this data on your WordPress site.<\/p><\/li>\n<\/ol>\n\nThe service is provided by Clixx CRM. See its terms of use at https:\/\/app.clixx.com.br\/terms-of-use.html and its privacy policy at https:\/\/app.clixx.com.br\/privacy-policy.html.<\/p>\n\n\n
\n- Upload the
clixxcrm<\/code> folder to \/wp-content\/plugins\/<\/code>, or install the plugin through the WordPress plugins screen.<\/li>\n- Activate the plugin from the Plugins screen.<\/li>\n
- Go to \"Clixx CRM\" in the admin menu and enter your email and API token.<\/li>\n
- After connecting, open \"Clixx CRM > Forms\" to copy the shortcode, iframe code or standalone HTML embed of each form.<\/li>\n<\/ol>\n\n\n
\nWhere do I get the API token?<\/h3><\/dt>\nInside Clixx CRM, go to Settings > API and generate a token.<\/p><\/dd>\n
Does the plugin store visitor data on my WordPress database?<\/h3><\/dt>\nNo. Form submissions are sent directly from the visitor's browser to your Clixx CRM via the public webhook endpoint.<\/p><\/dd>\n
Can I customize the look of the embedded form?<\/h3><\/dt>\nYes. The \"Embed HTML\" tab in each form has a built-in customizer with controls for button text, colors, spacing and typography, plus a live preview. The generated HTML is fully self-contained and can be pasted into any site (WordPress or not).<\/p><\/dd>\n
Is the plugin compatible with the block editor?<\/h3><\/dt>\nYes. The \"Clixx CRM Form\" block lets you pick a form from a dropdown and adjust the iframe height in the inspector panel.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.5.1<\/h4>\n\n\n- Plugin review compliance: (1) the admin menu icon CSS is no longer injected via
admin_head<\/code> \u2014 it is now registered via wp_register_style<\/code> \/ wp_enqueue_style<\/code> and wp_add_inline_style<\/code>, attached to a dedicated clixxcrm-menu-icon<\/code> handle that loads on every admin page; (2) added == External services ==<\/code> section to the readme documenting the connection to app.clixx.com.br<\/code> (\/api\/auth\/verify<\/code>, \/api\/anuncios<\/code>, \/api\/webhook\/inscricao\/{hash}<\/code>), what data is sent and when, plus links to the Clixx CRM Terms of Use and Privacy Policy; (3) the inline <style><\/code> \/ <script><\/code> tags inside the standalone Embed HTML snippet (which is meant to be COPY-PASTED into any external page, not enqueued by WordPress) are now assembled via concatenation and explicitly commented so they are not mistaken for WordPress front-end output.<\/li>\n<\/ul>\n\n1.5.0<\/h4>\n\n\n- Bug fix: o customizador JS (admin\/js\/admin.js) ignorava os campos personalizados e regenerava o embed s\u00f3 com nome\/email\/celular, sobrescrevendo o HTML gerado pelo PHP. Agora o JS l\u00ea os campos via
data-campos-extras<\/code> no container e injeta os campos extras no preview ao vivo e no c\u00f3digo copiado. Cores\/sliders preservam os campos.<\/li>\n<\/ul>\n\n1.4.9<\/h4>\n\n\n- Nome do plugin renomeado para \"Clixx CRM - Formul\u00e1rios para Capta\u00e7\u00e3o de Leads\" (mais descritivo no diret\u00f3rio do WordPress.org). Menu interno e marca seguem como \"Clixx CRM\".<\/li>\n<\/ul>\n\n
1.4.8<\/h4>\n\n\n- Embed HTML do an\u00fancio agora inclui os campos personalizados configurados no CRM (Cidade, Data de Nascimento, etc.). Suporta tipos: text, email, phone, cpf, cnpj, cep, number, date, textarea, select e checkbox. Requer CRM atualizado para retornar
campos_personalizados<\/code> em \/api\/anuncios<\/code> (j\u00e1 incluso). Limpe o cache do plugin (transient clixxcrm_anuncios<\/code>) para puxar os campos novos.<\/li>\n<\/ul>\n\n1.4.7<\/h4>\n\n\n- Text domain renamed from
clixxcrm<\/code> to clixx-crm<\/code> to match the plugin slug on WordPress.org. All __()<\/code>, _e()<\/code>, esc_html__()<\/code>, esc_attr_e()<\/code>, etc. calls and the Text Domain:<\/code> header + block.json textdomain<\/code> were updated. Internal slugs (menu URL, option keys, postMessage protocol) kept as clixxcrm<\/code>.<\/li>\n<\/ul>\n\n1.4.6<\/h4>\n\n\n- Removed
Plugin URI<\/code> from the plugin header (it pointed to the same URL as Author URI<\/code>, which the WordPress.org submission validator rejects). Once the plugin is published, the canonical plugin page is wordpress.org\/plugins\/clixxcrm\/<\/code>.<\/li>\n<\/ul>\n\n1.4.5<\/h4>\n\n\n- Cleaned up the diagnostic instrumentation from 1.4.3\/1.4.4: yellow debug bar removed from the live preview, console marker on script load removed, try\/catch wrapper around
renderPreview<\/code> removed. The cache-busting fix from 1.4.4 stays.<\/li>\n<\/ul>\n\n1.4.4<\/h4>\n\n\n- Fixed a bug in the build script where the
CLIXXCRM_VERSION<\/code> PHP constant was never being updated past 1.0.0<\/code> because of a too-strict regex (it required ')<\/code> with no whitespace between, but the source file had ' )<\/code>). Result: every release since 1.0.1 was shipped with the constant stuck at 1.0.0, which caused wp_enqueue_script(..., CLIXXCRM_VERSION)<\/code> to always emit ?ver=1.0.0<\/code>, so browsers reused the cached admin.js<\/code> from the very first install. All previous \"preview not updating\" reports were caused by browsers serving the old admin.js<\/strong>.<\/li>\n<\/ul>\n\n1.4.3<\/h4>\n\n\n- Added a visible build marker in the live preview (yellow bar with render counter and timestamp) and a console.log on script load. This is purely diagnostic for users who report the preview not updating \u2014 if the bar is missing, the browser\/WordPress is serving a cached old
admin.js<\/code>.<\/li>\n- Wrapped
renderPreview<\/code> in try\/catch with console.error<\/code> to surface any silent failures.<\/li>\n<\/ul>\n\n1.4.2<\/h4>\n\n\n- Live preview rebuilt with a third strategy: each preview container gets a unique ID, and every
.clx2-form<\/code> selector in the embed CSS is rewritten to #unique-id .clx2-form<\/code> before being injected. This gives the embed rules a specificity of (1,2,1)+<\/code>, beating any WordPress admin rule. No iframe, no Shadow DOM, no CSP edge cases \u2014 just plain DOM with rewritten selectors.<\/li>\n<\/ul>\n\n1.4.1<\/h4>\n\n\n- Live preview rebuilt on top of Shadow DOM. The previous iframe srcdoc approach failed silently in some hosting \/ CSP setups; Shadow DOM is native browser CSS isolation with no iframe and no timing dependency, so the preview now updates instantly when colors, sliders or font are changed.<\/li>\n<\/ul>\n\n
1.4.0<\/h4>\n\n\n- Plugin Check \/ WordPress.org compliance pass: readme rewritten in English, \"Tested up to\" bumped to 6.9, output escaping audited (
esc_attr<\/code> on every echo), $_POST<\/code> inputs run through sanitization helpers, view variables prefixed with clixxcrm_<\/code>, heredoc strings replaced with concatenation, load_plugin_textdomain()<\/code> removed (auto-loaded by core since 4.6).<\/li>\n- Preview now uses
iframe.srcdoc<\/code> instead of document.write()<\/code> for reliability across security plugins \/ CSP setups.<\/li>\n<\/ul>\n\n1.3.2<\/h4>\n\n\n- Preview rendered inside an
<iframe><\/code> to isolate the embedded form from WordPress admin global CSS rules. Without isolation, admin rules on input<\/code>, form<\/code>, button<\/code> were overriding the embed's own styles, so only text changes were visible.<\/li>\n- Sidebar menu icon now loads as URL (not data URI) so the original Clixx logo colors are preserved instead of WordPress applying its default
opacity: 0.6<\/code> overlay.<\/li>\n<\/ul>\n\n1.3.1<\/h4>\n\n\n- Live preview event listeners moved to document-level delegation. They are now reliable even when the customizer markup is inside collapsed panels or inactive tabs.<\/li>\n
- Automatic re-render when expanding the codes panel or switching to the Embed HTML tab.<\/li>\n<\/ul>\n\n
1.3.0<\/h4>\n\n\n- Embed HTML tab gained a full visual customizer (button text, colors, spacing, typography) with live preview and auto-generated code, identical to the one available inside the CRM.<\/li>\n
- Tab labels rendered with
mb_strtoupper<\/code> so accented characters such as \u00c3\/\u00c1<\/code> are uppercased correctly.<\/li>\n<\/ul>\n\n1.2.0<\/h4>\n\n\n- Full visual rewrite: header with logo, pill-style tabs (Connection \/ Forms \/ About) and a clean content card with rows.<\/li>\n
- Fixed CSS parsing bug from 1.1.0 caused by an inline SVG data URI in a CSS rule.<\/li>\n
- New About tab with version, license and feature summary.<\/li>\n<\/ul>\n\n
1.1.0<\/h4>\n\n\n- Modern indigo palette across the connect and forms screens.<\/li>\n
- Sidebar menu icon uses the official Clixx logo.<\/li>\n
- Forms screen lists each campaign with Shortcode, Iframe and Embed HTML tabs and a copy button.<\/li>\n<\/ul>\n\n
1.0.1<\/h4>\n\n\n- The Clixx CRM URL is fixed to
https:\/\/app.clixx.com.br<\/code>. Override at development time via define('CLIXXCRM_API_URL', '...')<\/code> in wp-config.php<\/code>.<\/li>\n<\/ul>\n\n1.0.0<\/h4>\n\n\n- Initial release: connection by email + API token,
[clixxcrm_formulario]<\/code> shortcode and Gutenberg block.<\/li>\n<\/ul>","raw_excerpt":"Connect your Clixx CRM account to WordPress and embed your campaign forms in any page or post.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/311191","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=311191"}],"author":[{"embeddable":true,"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/clixxcrm"}],"wp:attachment":[{"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=311191"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=311191"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=311191"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=311191"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=311191"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/ssw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=311191"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}