Easy UTM tracking with contact form 7 vs Flowblinq AI Boost

Easy UTM tracking with Contact Form 7 lets you track your marketing campaigns with one-click installation. When a visitor lands on your site through a tagged URL (Google Ads, Facebook Ads, email campaigns, etc.), the plugin stores the tracking parameters in first-party cookies and includes them in your Contact Form 7 lead emails, even if the visitor browses several pages before submitting the form. What gets captured utm_source, utm_medium, utm_term, utm_content, utm_campaign Ad click IDs: gclid (Google Ads), fbclid (Facebook), msclkid (Microsoft Ads), ttclid (TikTok) Landing page URL External referrer (the site the visitor actually came from) How it reaches you Zero-config: a formatted tracking table is appended to every CF7 email automatically (can be turned off). Mail tags: place [utm_source], [utm_medium], [utm_term], [utm_campaign], [utm_content], [utm_gclid], [utm_fbclid], [utm_msclkid], [utm_ttclid], [utm_landing], [utm_referrer] anywhere in your CF7 mail template, subject line included. Form Submissions log: every submission is saved under Contact → Form Submissions with its full attribution and submitted fields, so no lead is lost even if the notification email fails to send. Settings (Settings → Easy UTM CF7) Cookie lifetime (default 60 days) First-touch or last-touch attribution Turn the auto-appended email table on/off Turn the Form Submissions log on/off

77% of brands are invisible to AI search platforms. Loamly / PRWeb, 2025 Your WordPress site was built for humans. Flowblinq is performance automation for AI-specific web pages. The platform audits what ChatGPT, Claude, Perplexity, and Gemini say about your brand, writes the pages they need, and hosts them on Flowblinq. The plugin makes them available at your domain via WordPress rewrite rules. The system keeps every asset current as those platforms change what they reward. We audit, fix, and maintain for you. Automated after setup. Audit. What ChatGPT, Claude, Perplexity, and Gemini say about your brand. What they get right. What they miss. What they get wrong. Fix. Four AI-specific assets hosted on Flowblinq, served at your domain via WordPress rewrite rules: llms.txt, llms-full.txt, .well-known/ucp.json, and per-page Schema.org JSON-LD. Maintain. The Flowblinq backend monitors what AI platforms actually index, re-evaluates as signals shift, and rewrites your assets automatically. No scheduled regeneration on your server. No re-runs of the audit. Recent client deployments: National hospital network: 142,000 to 992,000 weekly page views, 6 weeks after Flowblinq deployment. Flowblinq client data, 2026 Indian distributor of a global photography brand: 5,800 to 14,700 weekly page views, 4 weeks after Flowblinq deployment. Flowblinq client data, 2026 Requires a Flowblinq account. Get credentials at www.flowblinq.com. External Services This plugin connects to geo.flowblinq.com, operated by Flowblinq. The service is the source of all served content. What is sent, when, and why: You click Run Free Audit. The plugin POSTs a JSON payload containing your site URL (e.g. https://yoursite.com) to https://geo.flowblinq.com/api/v1/audit. This starts the AI-visibility audit. You click Verify My Changes. The plugin POSTs an empty payload to https://geo.flowblinq.com/api/v1/audit/{audit_id}/verify, referencing the audit you started. This re-runs the audit for a before-and-after comparison. A visitor (human or AI crawler) requests /llms.txt, /llms-full.txt, or /.well-known/ucp.json. The plugin fetches the file from https://geo.flowblinq.com/api/serve/{your-site-slug}/... and caches the response for one hour. Only your site slug is sent. No visitor data. Authentication uses OAuth 2.0 client_credentials against https://geo.flowblinq.com/api/oauth/token. The Client ID and Client Secret are sent only in this request. The access token is cached in the WordPress transients table for under one hour. No visitor data is sent. The plugin transmits your site URL, your site slug, and your API credentials. It does not transmit visitor IP addresses, user agents, browsing history, form submissions, or any other end-user information. Service terms and privacy policy. By using this plugin you agree to the Flowblinq Terms of Service at https://flowblinq.com/terms and Privacy Policy at https://flowblinq.com/privacy. Privacy This plugin transmits the following data to geo.flowblinq.com, operated by Flowblinq: Your site URL when you start an audit. Your site slug when fetching /llms.txt and other GEO files for visitors. Your API credentials (Client ID and Client Secret) over HTTPS, only when requesting an access token. This plugin does not collect, store, or transmit: Visitor IP addresses, browsers, or session identifiers. End-user form submissions or comments. Personally identifiable information about anyone other than the site administrator who configures the plugin. Stored data on your WordPress site: fqgeo_client_id, fqgeo_client_secret, fqgeo_site_slug, fqgeo_active_audit_id in the wp_options table. Cached response payloads in the WordPress transients table (fqgeo_proxy_*, fqgeo_access_token). These expire within one hour. When you delete the plugin, uninstall.php removes all of the above.