
ADCT CONTACT CLICK TRACKER
ADCT Contact Click Tracker compatibility with REEID Translate
ADCT Contact Click Tracker compatibility with REEID Translate is being reviewed using official plugin documentation. Tracks visitor clicks on contact elements including WhatsApp, phone, showroom, floating buttons, and footer `tel:` links. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What ADCT Contact Click Tracker does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
ADCT Contact Click Tracker is documented in the Analytics category with 8 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How ADCT Contact Click Tracker compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Tracks visitor clicks on contact elements including WhatsApp, phone, showroom, floating buttons, and footer `tel:` links.
- Captures marketing attribution for each tracked click using a 30-day first-touch cookie covering UTMs, `gclid`, landing URL, and referrer.
- Groups tracked clicks into “one card per browser tab session,” preserving every click within the same session card.
- Stores tracking data in the site’s own WordPress database; does not send tracking data to external/third-party services.
- Hashes visitor IP addresses with SHA-256 before storage and does not retain plain-text IPs.
- Records country only when behind Cloudflare via the standard geo request header (Cloudflare-provided), without sending an IP address to obtain it.
- Optionally enriches WooCommerce product-page tracking with a product snapshot (title, price, mileage, image) when WooCommerce is present.
- Provides an admin reporting dashboard with Overview, Leads, and Sessions pages, including filters, pagination, and CSV export, with role-based access control for reporting.
TRANSLATION BOUNDARY
ADCT Contact Click Tracker capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
ADCT Contact Click Tracker and REEID Translate FAQ.
What does ADCT Contact Click Tracker do?
ADCT Contact Click Tracker has 8 documented features listed in its official documentation. See the Plugin Information section for details.
Does ADCT Contact Click Tracker have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from ADCT Contact Click Tracker?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate ADCT Contact Click Tracker in a multilingual WordPress workflow.
REEID documents ADCT Contact Click Tracker functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.