| 开发者 | kaxrist |
|---|---|
| 更新时间 | 2026年7月17日 18:19 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
tel:mailto:sms:geo: direction linksutm_source, utm_medium, utm_campaign, utm_term and utm_content. It also detects advertising click IDs from Google, Microsoft, Meta, TikTok, LinkedIn and Yandex to improve traffic-source classification.
Conversion dashboard
The local WordPress dashboard includes:
dataLayer event, an existing gtag function, or direct loading of gtag.js.
The dataLayer option does not load another Google script. The default installation does not contact Google or another analytics provider.
Frontend REST event endpoint
Logged-out visitors use protected frontend REST endpoints to submit conversion events. The endpoints do not expose dashboard data and apply short-lived tokens, same-site checks, validation, duplicate handling and rate limiting.
ccd-traffic-sources folder to /wp-content/plugins/.Traffic attribution connects a conversion with the marketing source that helped generate it. CCD Traffic Sources shows the source, medium, campaign, referrer and landing page associated with a form submission or contact click.
No. UTM tracking is included, but the plugin also detects referrers, search, direct visits, paid click IDs and contact conversions. It combines this information in a local conversion attribution dashboard.
Yes. UTM parameters provide clearer campaign names, but CCD Traffic Sources can also classify visits from referrer data, search engines, known social platforms, advertising click IDs and direct traffic.
The plugin detects Elementor, Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Avada Forms, Formidable Forms, Ninja Forms, WPBakery-rendered forms and standard HTML forms. Reliable AJAX success tracking depends on the success events exposed by each form plugin.
For supported AJAX integrations, the plugin waits for a reliable success event when one is available. For generic forms, a conversion is recorded when the browser reports that the form is valid and its submit event fires; a later server-side rejection may not be visible to the tracker.
No. The conversion tracker does not collect form field values such as name, email, phone number or message. It stores attribution and conversion metadata such as form system, form ID, page, campaign and traffic source.
It tracks clicks on supported phone, email, SMS, chat and direction links. It does not know whether a phone call was answered or whether a message was ultimately sent.
Only if an administrator enables GA4/GTM events. The default method for sites using Google Tag Manager is the local dataLayer event, which lets the existing GTM container control what is sent.