Lýsing
CoreTech Contact Buttons, Chat, Calls & Tracking helps site owners add a clear floating contact path without a heavy setup process.
Use it to show:
- A WhatsApp button with a configurable number and prefilled message.
- A call button with a configurable phone number.
- A display mode to show WhatsApp only, call only, or both buttons.
- Sequential rich tooltips for WhatsApp and call buttons.
- Tooltip customization for text color, background color, font size, first tooltip, initial delay, show time, transition gap, and repeat pause.
- Basic desktop/mobile visibility controls.
- Left or right bottom placement.
- Optional anonymous local click totals for WhatsApp and call clicks, with simple dashboard date filters.
- Optional separate WhatsApp and call GA4/GTM event output for sites already using Google Analytics or Google Tag Manager.
- Basic CTA tooltip styling and timing controls.
This WordPress.org build is fully functional on its own. It does not require a license key, trial, remote activation, or paid unlock.
Local click totals are stored only as anonymous aggregate WhatsApp and call counts in the WordPress database, including daily aggregate buckets for dashboard filters. The plugin does not store visitor identity, IP addresses, page URLs, message text, or wp-admin activity.
External services
When a visitor clicks the WhatsApp button, the visitor is sent to a WhatsApp URL so they can start a chat. The plugin does not send data to WhatsApp automatically in the background. The visitor’s browser or device contacts WhatsApp only after the visitor clicks the WhatsApp button.
Data sent when clicked: the configured WhatsApp number and optional prefilled message in the WhatsApp URL.
Service provider: WhatsApp LLC / Meta Platforms.
Terms of Service: https://www.whatsapp.com/legal/terms-of-service
Privacy Policy: https://www.whatsapp.com/legal/privacy-policy
Google Analytics / Google Tag Manager
The plugin does not load Google Analytics, Google Tag Manager, or Google API scripts. It does not include Measurement Protocol, OAuth, server-side conversion uploads, or wp-admin analytics tracking.
If the site owner already uses Google Analytics or Google Tag Manager, they may optionally enable frontend click events for WhatsApp and call buttons. In that case, the plugin sends one configured browser-side event name through the existing gtag() function when available, otherwise as one dataLayer event for GTM-only installs.
Data made available when enabled: separate WhatsApp/call event names, button type, button label, plugin source, and clicked link URL.
Service provider: Google LLC.
Terms of Service: https://policies.google.com/terms
Privacy Policy: https://policies.google.com/privacy
Uppsetning
- Upload the plugin zip through the WordPress Plugins screen, or extract it to
/wp-content/plugins/coretech-contact-buttons-chat-calls-tracking/. - Activate the plugin through the Plugins screen.
- Go to CoreTech or Settings > CoreTech Contact Buttons.
- Add your WhatsApp number or call number and save.
SOS
-
Does this plugin require a license key?
-
No. This WordPress.org build is fully functional and does not require a license key.
-
Does the plugin track wp-admin usage?
-
No. This build does not track wp-admin usage and does not phone home.
-
What click tracking is included?
-
The dashboard stores anonymous aggregate totals for WhatsApp and call button clicks locally in the WordPress database only. You can filter the dashboard by all time, today, last 7 days, last 30 days, or this month.
-
Does the GA4 helper send data to Google by itself?
-
No. The optional GA4/GTM helper only emits separate frontend click events when a visitor clicks WhatsApp or call buttons and the helper is enabled. It does not load Google scripts, call Google APIs, or track wp-admin usage. A site owner must already have Google Analytics, Google Tag Manager, or another tag setup for anything to be sent to GA4.
-
Can the WhatsApp prefilled message use HTML?
-
No. WhatsApp prefilled messages are sent through a WhatsApp URL as plain text. The plugin includes CTA tooltip style controls for text color, background color, and font size instead.
-
Does the plugin send lead data to a remote API?
-
No. This build does not include lead capture, CRM sync, ad sync, webhooks, or remote analytics APIs.
Umsagnir
Þátttakendur & höfundar
“CoreTech Contact Buttons, Chat, Calls & Tracking” er opinn hugbúnaður. Eftirfarandi aðilar hafa lagt sitt af mörkum við smíði þessarar viðbótar.
HöfundarTranslate “CoreTech Contact Buttons, Chat, Calls & Tracking” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Breytingarsaga
1.2.45
- Hardened settings persistence so saved GA4 IDs and custom click event names survive plugin updates and reinstall transitions.
- Added a local settings backup copy used only to restore saved configuration if the primary option is missing.
- Preserved existing GA4 click settings during partial settings saves.
1.2.44
- Added tooltip initial delay and repeat pause controls to the free build.
- Wired tooltip timing controls into the frontend sequence through safe data attributes.
- Updated plugin descriptions to mention tooltip customization.
1.2.43
- Restored the visible Premium Version link under the plugin name on the Plugins screen.
1.2.42
- Prepared the WordPress.org package for the approved coretech-contact-buttons-chat-calls-tracking slug.
- Silenced the read-only dashboard filter nonce warning with an inline reviewer note.
- Hardened frontend widget attribute output for Plugin Check escaping review.
1.2.41
- Added local dashboard filters for all time, today, last 7 days, last 30 days, and this month.
- Stored only anonymous daily aggregate click buckets for the new filters.
- Aligned dashboard metric cards so click numbers sit consistently across cards.
1.2.40
- Sent optional GA4 click events on pointerdown before WhatsApp or phone navigation begins.
- Increased the navigation handoff delay so Google Tag Assistant has more time to display the configured event.
- Hardened click target detection for nested SVG/text clicks.
1.2.39
- Moved frontend configuration from inline localized JavaScript into widget data attributes for better CSP compatibility.
- Added a CSP-safe dataLayer command fallback only when the gtag helper function is unavailable.
1.2.38
- Restored automatic GA4 Measurement ID detection for sites that already load GA4 through another plugin or snippet.
- Kept optional click events on direct gtag send_to only, with no generic dataLayer fallback.
1.2.37
- Required a valid GA4 Measurement ID before frontend Google events can be emitted.
- Removed the generic dataLayer fallback so loose GTM or Google tag rules cannot duplicate plugin click events.
- Kept local dashboard click totals independent from optional Google event output.
1.2.36
- Moved frontend button click handling to window capture so stale document/body listeners from older cached builds cannot fire after this build.
1.2.35
- Added a GA4 Measurement ID field so custom click events can be pinned to one GA4 destination instead of Google tag fan-out.
- Improved automatic GA4 ID detection from dataLayer, gtag script URLs, and inline gtag config.
- Captured plugin button clicks before older cached plugin listeners can fire, preventing stale-script duplicate events.
- Made frontend buttons slightly smaller and tooltip bubbles wider.
1.2.34
- Added a frontend listener guard and per-click de-dupe so cached or repeated script execution cannot send duplicate plugin events.
- Scoped direct gtag events to the detected GA4 G- destination when available to avoid broadcasting the same event to multiple Google destinations.
- Tightened click targeting so each button click can only use its own configured event name.
1.2.33
- Sent enabled frontend click events through exactly one available route: gtag when present, otherwise dataLayer for GTM-only installs.
- Kept WhatsApp opening in a new window/tab after the click event is queued.
- Kept side tooltips lower beside the active button.
1.2.32
- Restored direct gtag event sending so Google Tag Assistant can detect the configured custom events again.
- Kept custom event sending to one route only to avoid plugin-side duplicate events.
- Lowered the side tooltip position so it appears beside the active button instead of above it.
1.2.31
- Sent one dataLayer event only per plugin click to avoid duplicate custom events.
- Forced WhatsApp navigation to open in a new window/tab after the tracking event is queued.
- Moved tooltip bubbles beside the buttons instead of directly above them.
1.2.30
- Reduced frontend GA4/GTM click sending to one channel per click to prevent duplicate custom events.
- Updated local dashboard click totals to record aggregate button clicks automatically.
- Moved tooltip bubbles toward the top-left of the buttons.
- Increased the tooltip transition gap to two seconds.
1.2.29
- Styled button icons as circular badges inside each button with stronger theme-safe colors.
- Added exact configured event names to each frontend button.
- Sent enabled click events through gtag when present and dataLayer for GTM, so Tag Assistant can show the configured call and WhatsApp event names.
- Added a short call-link delay so the call event can fire before tel navigation opens.
1.2.28
- Replaced text placeholders with real inline WhatsApp and call SVG icons.
- Improved frontend dataLayer tracking so Tag Assistant can detect enabled click events before navigation.
- Added safe rich tooltip formatting for bold, italic, underline, line breaks, and inline color/font-size styles.
- Added sequential tooltip rotation with call-first defaults, four-second display time, and one-second transition gap.
1.2.27
- Rebuilt the final free archive as one exact-path package for the confirmed cPanel folder name.
- Packaged with WordPress-safe archive paths for cleaner activation and replacement.
1.2.26
- Updated the Plugins screen premium link to the Core Plugin Tech bundle page.
- Rebuilt final free replacement archives using exact legacy path variants for existing installs.
1.2.25
- Added a display mode setting for showing WhatsApp only, call only, or both buttons.
- Updated frontend rendering so the selected display mode controls which saved button appears.
1.2.24
- Added safe local migration for WhatsApp and call numbers from older cPanel installs so frontend buttons keep showing after replacement.
1.2.23
- Hardened the internal free build class and constants to avoid activation collisions with older separately installed copies.
1.2.22
- Split optional dataLayer event names into separate WhatsApp and call events.
- Added CTA tooltip style controls for text color, background color, and font size.
1.2.21
- Changed the WordPress left admin menu label to CPT MessageOps.
1.2.20
- Added an optional local click dashboard for WhatsApp and call clicks.
- Added a small tracking help section for using frontend dataLayer events with GA4 / Google Tag Manager.
- Kept local click tracking off by default and avoided remote analytics/API calls.
1.2.19
- Linked the plain Plugins screen premium note to the Core Plugin Tech website.
1.2.18
- Added a plain Plugins screen note that a premium version is available separately.
1.2.17
- Restored a top-level CoreTech admin menu for sites replacing the previous cPanel package.
1.2.16
- Added a high-version replacement build for sites still installed under the previous cPanel folder name.
1.2.07
- Refreshed the clean WordPress.org package and legacy replacement package so old upload filenames no longer contain the commercial interface.
1.2.06
- Rebuilt the install archive with WordPress-compatible forward-slash paths.
- Kept the same focused free feature set: WhatsApp, call, tooltip, placement, and basic visibility controls.
1.2.05
- Rebuilt the WordPress.org package as a focused, fully functional contact-button plugin.
- Kept the feature set simple: WhatsApp, call, tooltip, placement, and basic visibility controls.
- Improved the package structure so styles and scripts load through WordPress enqueue functions.

