FAQ & Troubleshooting

From your WordPress Dashboard, go to Plugins > Add New. Search for ClickIntent and install the free version directly from WordPress plugin repository. Activate the plugin and that's it. You will see "ClickIntent" in your menu bar.

If you have purchased the Pro version, you can download the "clickintent-pro.zip" plugin file by visiting https://getclickintent.com/my-account where your license details and download link will be visible. After downloading the zip file, head back to your WordPress Dashboard → Plugins → Add Plugin. There is a "Upload Plugin" button at the top. Upload the "clickintent-pro.zip" and activate. Make sure you have ClickIntent free plugin active before activating the pro plugin.

Check the following in order:

• Make sure the plugin is active in Plugins → Installed Plugins.
• Confirm the Section ID in your shortcode exactly matches the ID shown in ClickIntent → Section CTAs — it is case-sensitive and must be the slug, not the label.
• Check that the page actually supports shortcodes. Some page builders require a Shortcode block or element rather than pasting into a text block.
• Try switching to a default WordPress theme temporarily to rule out a theme conflict.

ClickIntent only loads its frontend script on pages that contain a [clickintent] shortcode. It doesn't add anything to pages where the shortcode isn't used.

The script is lightweight and all event tracking calls use non-blocking fetch() requests — analytics failures never delay the page or user interactions.

Yes. Use a Shortcode widget or element in your page builder and paste the [clickintent id="your-id"] shortcode into it. Both Elementor and Divi support this natively.

Yes — place as many [clickintent] shortcodes as you like on a single page, using the same or different Section IDs. Each tracks independently.

First, verify that the shortcode is rendering by visiting the page as a logged-out visitor and clicking the button yourself. Then:

• Check that the WordPress REST API is not disabled. ClickIntent uses the REST API (/wp-json/clc/v1/) to record events. Some security plugins block it — add an exception for ClickIntent's endpoints.
• Open your browser's Developer Tools → Network tab, click the button, and look for a request to /wp-json/clc/v1/event. If it returns a non-200 status, the response body will indicate why.
• If you use a CDN or caching plugin, make sure REST API endpoints are not being cached.

ClickIntent tracks all visitors, including you. To avoid counting your own visits during testing, use a browser extension to block the REST API calls, test in a private/incognito window on a different network, or temporarily deactivate the plugin while setting up your pages.

There is currently no built-in logged-in user exclusion, but this is planned for a future release.

No. Deactivating the plugin leaves all your leads, events, and settings completely intact. Data is only removed if you uninstall the plugin and you have enabled Delete all data on uninstall in ClickIntent → Settings beforehand.

The most common causes:

• The free plugin is not active. Pro requires both plugins to be installed and active simultaneously. Check Plugins → Installed Plugins.
• Your license has not been activated. Go to ClickIntent → Pro License and enter your license key. Pro features only unlock after successful license verification.
• The free plugin version is outdated. Pro v1.1.0 requires the free plugin to be at version 1.1.0 or higher.

The number of simultaneous site activations depends on the subscription plan you purchased. Check your account page on the ClickIntent website for the activation limit for your plan. You can deactivate a license from one site via ClickIntent → Pro License → Deactivate and then activate it on another.

Check these common causes:

• Your endpoint URL is wrong or not publicly accessible. ClickIntent validates that webhook URLs point to public IP addresses — local or private network addresses are rejected.
• Your endpoint is returning a non-2xx HTTP status. Check the response body in the webhook logs table for details from your endpoint.
• Your endpoint is timing out. Make sure your receiving server responds quickly. ClickIntent waits a limited time for a response before marking the delivery failed.

Use the Retry button in the webhook logs table to re-send any failed delivery manually.

If you have enabled geolocation tracking in ClickIntent → Settings, the plugin transiently sends a visitor's IP address to ip-api.com to resolve their approximate country, region, and city. The IP address is used only for this lookup and is never stored in your database — only the resolved location data is saved. Geolocation tracking is disabled by default and only active if you explicitly enable it.

No other data is sent to external servers by the free plugin. If you use Pro's webhook feature, data is sent to the URL you configure — that is entirely under your control.

ClickIntent does not store IP addresses. If you enable geolocation tracking in ClickIntent → Settings, approximate location data (country, region, city) is stored alongside click events — no IP address is ever written to your database. This location data may still be considered personal data under GDPR depending on its precision and context. You are responsible for:

• Disclosing geolocation data collection in your Privacy Policy if you have enabled the feature.
• Ensuring you have a lawful basis for processing (e.g. legitimate interest or consent).
• Responding to subject access and deletion requests — leads can be deleted individually from the Leads page.

ClickIntent does not provide legal advice. Consult a qualified privacy professional for compliance guidance specific to your situation.

Yes. ClickIntent includes a hidden honeypot field in the lead capture form that is invisible to real visitors but will typically be filled in by automated bots. Submissions where this field is populated are silently rejected server-side without being stored.

In addition, server-side rate limiting is applied: the lead form endpoint accepts a maximum of 10 submissions per IP address per 60-second window. Requests exceeding this limit are rejected automatically.

Yes. On multisite installations, each sub-site maintains its own separate leads, events, and section configurations. On uninstall, data is cleaned up across all sites in the network.