The Dashboard's Conversions and Conversion Rate cards have been replaced with AI Traffic Sessions. Both removed cards always showed zero on every site; this plugin has never included conversion tracking.<\/p>","1.2.0":"
If you previously enabled Delete on uninstall, re-check that setting after updating. Earlier versions saved this setting but did not act on it; this version makes it function correctly for the first time.<\/p>","1.0.0":"
Initial release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3580414,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3580414,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3580414,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3580414,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.3.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3580414,"resolution":"1","location":"assets","locale":"","width":800,"height":545},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3580414,"resolution":"2","location":"assets","locale":"","width":800,"height":731},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3580414,"resolution":"3","location":"assets","locale":"","width":800,"height":724}},"screenshots":{"1":"Dashboard tab showing summary metric cards and the channel share pie chart.","2":"Reports tab with session log, filters, and CSV export.","3":"Settings tab showing retention, consent, and privacy configuration."}},"plugin_section":[],"plugin_tags":[256047,9067,40006,4131,268178],"plugin_category":[36],"plugin_contributors":[268179],"plugin_business_model":[],"class_list":["post-328423","plugin","type-plugin","status-publish","hentry","plugin_tags-ai-traffic","plugin_tags-attribution","plugin_tags-marketing-attribution","plugin_tags-referrer","plugin_tags-traffic-channels","plugin_category-analytics","plugin_contributors-hdfraser","plugin_committers-hdfraser"],"banners":{"banner":"https:\/\/ps.w.org\/cqi-referrer-attribution\/assets\/banner-772x250.png?rev=3580414","banner_2x":"https:\/\/ps.w.org\/cqi-referrer-attribution\/assets\/banner-1544x500.png?rev=3580414","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/cqi-referrer-attribution\/assets\/icon-128x128.png?rev=3580414","icon_2x":"https:\/\/ps.w.org\/cqi-referrer-attribution\/assets\/icon-256x256.png?rev=3580414","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/cqi-referrer-attribution\/assets\/screenshot-1.png?rev=3580414","caption":"Dashboard tab showing summary metric cards and the channel share pie chart."},{"src":"https:\/\/ps.w.org\/cqi-referrer-attribution\/assets\/screenshot-2.png?rev=3580414","caption":"Reports tab with session log, filters, and CSV export."},{"src":"https:\/\/ps.w.org\/cqi-referrer-attribution\/assets\/screenshot-3.png?rev=3580414","caption":"Settings tab showing retention, consent, and privacy configuration."}],"raw_content":"\n
Most analytics plugins guess where your traffic came from by running a script in the visitor's browser, after the page has already loaded, and after any ad blocker or privacy extension has had a chance to block it. CQI Referrer Attribution classifies every visit on the server, before the page is even sent, so the data is complete and the plugin adds no client-side JavaScript, no extra request, and no Core Web Vitals penalty.<\/p>\n\n
It also answers a question most attribution tools still miss: how much of your traffic is coming from AI assistants. ChatGPT, Gemini, Perplexity, Claude, Copilot, and a growing list of others now send real visitors. This plugin classifies that traffic as its own channel, not lumped into Direct or Referral where it disappears.<\/p>\n\n
Nine channels are detected automatically: AI Tools, Organic Search, Social Media, Email, Paid Search, Paid Display, Campaign, Referral, and Direct.<\/p>\n\n
This plugin is fully functional with no licence key, trial period, or usage limit of any kind.<\/p>\n\n
AI Referrer Taxonomy<\/strong><\/p>\n\n A built-in registry of AI assistant domains is used to classify AI-referred traffic. The default set includes ChatGPT, Google Gemini, Perplexity, Claude, Microsoft Copilot, Grok, Meta AI, and more. Entries can be added, edited, activated, deactivated, deleted, and exported as JSON.<\/p>\n\n Dashboard<\/strong><\/p>\n\n A 30-day summary showing total sessions, session change versus the previous 30 days, AI traffic sessions and their share of total traffic, top channel, and a channel share pie chart.<\/p>\n\n Sessions log<\/strong><\/p>\n\n The full Sessions report supports date range, channel, and source filters, pagination, and CSV export.<\/p>\n\n Consent-aware<\/strong><\/p>\n\n When CQI Consent is active, attribution is only persisted after marketing consent is granted. Without consent, classification runs in memory only and no cookie or database row is written. The plugin operates in permissive mode when CQI Consent is not installed.<\/p>\n\n Privacy by design<\/strong><\/p>\n\n No personal data is stored. Session tokens are HMAC-SHA256 hashes of an anonymized IP address (last octet zeroed) and the current date. Raw IP addresses are never written to disk. Token rotation is daily. The plugin is registered with the WordPress personal data export and erasure framework.<\/p>\n\n Excluded channels<\/strong><\/p>\n\n Any channel can be excluded from the Dashboard summary, the channel share chart, and the Sessions report. This is most useful for removing Direct \/ Unknown from view so reports focus on traffic you can actually attribute and act on.<\/p>\n\n Path exclusions and bot filtering<\/strong><\/p>\n\n A built-in guard silently drops requests to Public PHP API<\/strong><\/p>\n\n Two functions are available for use in themes and other plugins:<\/p>\n\n These function names are intentionally preserved from CQIP Site Services v1.8.0 for backward compatibility on sites migrating from that plugin.<\/p>\n\n Filter and action hooks<\/strong><\/p>\n\n These hooks let other plugins extend this plugin's behaviour. They are not used by this plugin itself; they exist for add-ons such as CQI Referrer Attribution Pro.<\/p>\n\n CQI (Content Quality and Intelligence) is a methodology standard that is followed, not a technology stack. Implementations can exist for static PHP sites, WordPress, page generators, and other document management systems. Its purpose is to encourage structured content that benefits human and machine readers.<\/p>\n\n\n No configuration is required after activation. Classification begins on the next front-end page request.<\/p>\n\n\n No. Classification is entirely server-side. No tracking scripts are added to the front end.<\/p><\/dd>\n No. Session tokens are one-way cryptographic hashes (HMAC-SHA256) of an anonymized IP address and the current date. Raw IP addresses are never stored. Tokens cannot be reversed to identify an individual.<\/p><\/dd>\n Not at the same time, if CQIP Site Services has its own Referrer Attribution module active. Both write to the same database tables, since this plugin was extracted from that module and preserves its table and option names for migration compatibility. If When a visitor arrives via a referrer that matches an entry in the AI Referrer Taxonomy, the session is classified as the AI Tools channel. The matched platform name (e.g. \"ChatGPT\") is stored as the source. The default taxonomy includes 17 entries and can be edited from the AI Taxonomy tab.<\/p><\/dd>\n The plugin does not store personal data and is registered with the WordPress personal data export and erasure framework. When CQI Consent is active, attribution is only persisted after marketing consent. As with any tool that processes visitor data, your own legal assessment of your site's practices is advisable.<\/p><\/dd>\n Visits with no referrer and no UTM parameters are classified as the Yes. Go to Attribution > Settings > Excluded channels<\/strong> and check any channels you want removed. Excluded channels are removed from the Dashboard summary cards, the channel share chart, and the Sessions report, including CSV export. This is commonly used to exclude Direct \/ Unknown so reports focus on attributable traffic.<\/p><\/dd>\n By default, nothing is removed. Your attribution data, settings, and AI taxonomy stay in the database in case you reinstall later. If you want a clean removal, enable Attribution > Settings > Data and Storage > Delete data on uninstall<\/strong> before deleting the plugin. With that enabled, deleting the plugin permanently removes the attribution log, all plugin settings, and the AI taxonomy. This cannot be undone.<\/p><\/dd>\n Go to Attribution > Settings > Path Exclusions<\/strong>. Add one path prefix per line. Any request whose URL starts with a listed path is silently dropped before classification runs. Common entries are When more than one signal is present on a session, this priority order applies:<\/p>\n\n Both are detected from the If your paid traffic does not carry UTM parameters, those sessions are classified by referrer instead, typically landing in Organic Search, Referral, or Direct depending on the source. Tagging every paid URL with UTM parameters is required for accurate Paid Search and Paid Display classification.<\/p><\/dd>\n\n<\/dl>\n\n\n\/robots.txt<\/code>, \/sitemap.xml<\/code>, \/xmlrpc.php<\/code>, \/favicon.ico<\/code>, and other system paths before classification runs. Additional path prefixes can be added in Settings, one per line, to suppress noise from any crawlers or automated probes specific to your site.<\/p>\n\n\n
cqip_attr_get_channel()<\/code>, returns the current visitor's channel slug<\/li>\ncqip_attr_get_source()<\/code>, returns the full attribution array<\/li>\n<\/ul>\n\n\n
cqi_referrer_attribution_logo_url<\/code> (filter), the mark shown in the admin page header<\/li>\ncqi_referrer_attribution_plugin_name<\/code> (filter), the page title shown in the admin page header<\/li>\ncqi_ra_session_logged<\/code> (action), fires after each session is recorded, receives the new row's ID and data<\/li>\ncqi_ra_admin_tabs<\/code> (action), fires inside the admin page's tab navigation, after the built-in tabs<\/li>\ncqi_ra_unknown_tab_handled<\/code> (filter), fires when an unrecognized tab slug is requested, lets an add-on render its own tab body<\/li>\ncqi_ra_sessions_view_filters<\/code> (filter), the Sessions report's query filters, before the session log is queried; also applied before CSV export runs<\/li>\ncqi_ra_sessions_filter_bar<\/code> (action), fires inside the Sessions filter bar, after the built-in filter fields<\/li>\ncqi_ra_sessions_table_header<\/code> (action), fires inside the Sessions table header row, after the built-in columns<\/li>\ncqi_ra_sessions_table_row<\/code> (action), fires inside each Sessions table row, after the built-in columns, receives the row object<\/li>\ncqi_ra_dashboard_log_id_in<\/code> (filter), restricts Dashboard metrics to a specific list of session row IDs<\/li>\n<\/ul>\n\nWhat is CQI?<\/h3>\n\n
\n
cqi-referrer-attribution<\/code> folder to \/wp-content\/plugins\/<\/code>.<\/li>\n\n
Does this plugin use JavaScript to track visitors?<\/h3><\/dt>\n
Does this plugin store personal data?<\/h3><\/dt>\n
I have CQIP Site Services installed. Can I run both?<\/h3><\/dt>\n
CQIP_SS_ENABLE_REFERRER<\/code> is set to true<\/code> in your wp-config.php<\/code>, this plugin detects that and refuses to activate, showing an admin notice with the exact line to add to wp-config.php<\/code> to resolve it. Existing attribution data carries over automatically once the conflict is resolved.<\/p><\/dd>\nHow does the AI channel work?<\/h3><\/dt>\n
Will this work with GDPR \/ UK-GDPR?<\/h3><\/dt>\n
What happens if a visitor does not have a referrer?<\/h3><\/dt>\n
direct<\/code> channel.<\/p><\/dd>\nCan I remove Direct \/ Unknown, or any other channel, from reports?<\/h3><\/dt>\n
What happens to my data if I delete the plugin?<\/h3><\/dt>\n
How do I stop bot probes and crawler noise appearing in the session log?<\/h3><\/dt>\n
\/robots.txt<\/code>, \/sitemap.xml<\/code>, \/feed\/<\/code>, and any path your monitoring tools or uptime checkers hit. The plugin also has a built-in guard that automatically excludes \/xmlrpc.php<\/code>, \/wp-cron.php<\/code>, \/wp-signup.php<\/code>, \/favicon.ico<\/code>, and other WordPress system paths regardless of your exclusion list.<\/p><\/dd>\nWhat is the channel priority order?<\/h3><\/dt>\n
\n
How are Paid Search and Paid Display detected?<\/h3><\/dt>\n
utm_medium<\/code> URL parameter, not from the referrer header. utm_medium<\/code> set to cpc<\/code> or ppc<\/code> is classified as Paid Search. utm_medium<\/code> set to display<\/code> is classified as Paid Display. Any other utm_medium<\/code> value is classified as Campaign.<\/p>\n\n1.4.2<\/h4>\n\n
\n
1.4.1<\/h4>\n\n
\n
1.4.0<\/h4>\n\n
\n
1.3.3<\/h4>\n\n
\n
1.3.2<\/h4>\n\n
\n
1.3.1<\/h4>\n\n
\n
1.3.0<\/h4>\n\n
\n
1.2.3<\/h4>\n\n
\n
1.2.2<\/h4>\n\n
\n
1.2.1<\/h4>\n\n
\n
1.2.0<\/h4>\n\n
\n
1.1.2<\/h4>\n\n
\n
1.1.1<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
1.0.12<\/h4>\n\n
\n
1.0.11<\/h4>\n\n
\n
1.0.10<\/h4>\n\n
\n
1.0.9<\/h4>\n\n
\n
1.0.8<\/h4>\n\n
\n
1.0.7<\/h4>\n\n
\n
1.0.6<\/h4>\n\n
\n
1.0.5<\/h4>\n\n
\n
1.0.4<\/h4>\n\n
\n
1.0.3<\/h4>\n\n
\n
1.0.2<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n