| 开发者 | kaxrist |
|---|---|
| 更新时间 | 2026年7月9日 22:06 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
tel:mailto:sms:geo:utm_source, utm_medium, utm_campaign, utm_term and utm_contentdataLayer mode that does not load another Google scriptccd-traffic-sources folder to /wp-content/plugins/, or install the plugin zip through Plugins > Add New.No. The plugin can capture UTM/source data and fill supported hidden fields, but its main purpose is a local conversion attribution dashboard for enquiries and contact actions.
Phone, email, SMS, WhatsApp, Telegram, Viber, Messenger and direction links are detected from their URL format. Existing buttons and widgets usually work without changing the link. Buttons that trigger contact actions only through custom JavaScript can use the manual tracking API.
It works with regular frontend POST forms and includes detection labels for Elementor, Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Formidable Forms, Ninja Forms and WPBakery-rendered forms. Unsupported forms are still tracked as generic forms when they submit normally.
For generic forms, the event is recorded after the browser says the form is valid and the submit event fires. For supported AJAX flows, the plugin listens for successful submission events where available. Some custom forms can still reject a submission server-side without exposing a reliable frontend success event, so treat form tracking as a conversion signal rather than an authoritative CRM lead total.
Use the manual JavaScript API after the frontend tracker is loaded:
window.CCDTrafficSources.track({ event: 'whatsapp_click', target: 'https://wa.me/...' });
The event value should be one of the supported event types, such as form_submit, tel_click, mailto_click, whatsapp_click, viber_click, messenger_click or directions_click.
The dashboard fills only after a visitor submits a tracked form or clicks a supported contact link. It does not import old analytics data and it does not count ordinary pageviews.
Only if you enable GA4 events in Settings. The default and recommended method for sites using Google Tag Manager is dataLayer, which lets GTM handle the final GA4 event without the plugin loading gtag.js.
The retention setting can delete events after 90, 180 or 365 days, or keep them until they are manually removed. The default is 365 days. Uninstalling the plugin removes plugin options, scheduled cleanup events and the custom event table.
The default Sourcebuster mode is Auto Detect. When another plugin already provides a compatible window.sbjs instance, CCD Traffic Sources reuses it instead of loading another copy.