Beetle Tracking – Cloudflare Zaraz for WooCommerce
Beetle Tracking: Plug and Play Server-Side Tracking for WordPress Are you tired of spending money on high-cost marketing campaigns that aren’t delivering results? Beetle Tracking gives you the clear view you need to understand your website visitors and target your campaigns more effectively. The Blurry Vision Problem Imagine you’re the owner of a thriving online store. You’ve got amazing products, and you want to attract as many customers as possible, but you’re wearing blurry glasses. This means you can’t see your customers clearly, so you can’t market your products effectively. The Solution: New Crystal Clear Glasses Introducing Beetle Tracking, your new pair of marketing glasses.It helps you see your customers clearly, so you can understand their needs and preferences better. This means you can target your marketing efforts more accurately and spend less money on advertising. With Beetle Tracking, you’ll be able to connect with your customers on a deeper level and increase your sales. Beetle Tracking is your most dedicated employee. It works tirelessly behind the scenes to collect accurate data, so you can make informed decisions and grow your business. Key Benefits of Beetle Tracking: ✅ 20-40% More Accurate Data: With Beetle Tracking’s server-side tracking, you capture up to 40% more data than traditional client-side methods, which are often blocked by ad blockers or restricted by browsers. This gives you a more complete understanding of your users’ behavior, directly improving your marketing insights. ✅ Boost Your Ad Campaigns: More accurate data fuels the algorithms behind Google Ads, Facebook, and other advertising platforms. This leads to higher conversion rates, as you can fine-tune your targeting, resulting in better-performing campaigns and more return on your ad spend. ✅ Lower Ad Costs: By leveraging the full potential of server-side tracking, you cut wasted ad spend. With enhanced data accuracy, you can spend less on ads while achieving better results, maximizing the efficiency of your campaigns. ✅ Simple Plug-and-Play effortless Setup: Unlike other server-side tracking solutions on the market, which often require complex setups and tech specialists, Beetle Tracking is designed for non-tech users, webshop owners, marketing people and agencies. It’s an easy-to-install WordPress plugin that gets you up and running in minutes – no coding or expertise required. ✅ Faster Site Speed: By moving tracking processes to the server, Beetle Tracking reduce the load on your customer’s browser, making it faster and more responsive for visitors, ensuring a smoother user experience. This leads to lower bounce rates and more engagement. ✅ Enhanced Privacy Compliance: Stay ahead of privacy regulations like GDPR and CCPA. With server-side tracking, you’re in control of user data and can securely manage how it’s processed. ✅ Works with All Popular Platforms: Easily integrate with platforms like Google Analytics, Meta Pixel (Facebook), Google Ads, LinkedIn, Pinterest, Bing and TikTok without technical headaches. ✅ Free and Pro Versions: Start with the free version of Beetle Tracking to enhance your tracking, or upgrade to the Pro version to unlock powerful features like: Beetle Consent: A GDPR-compliant, customizable cookie banner that helps you collect valid consents from all users, ensuring full compliance with privacy laws. Gravity Forms Tracking: Automatically track form submissions with form ID and title, working seamlessly with both AJAX and traditional page reload submissions. Page Scroll Measurement: Gain deeper insights into how far users scroll on your pages and optimize content accordingly. Conversion Recovery: With Pro, Beetle Tracking ensures you capture purchase events even when users don’t return to the “thank you” page. By matching checkout information with the payment gateway’s order status, purchase data is sent server-to-server, ensuring complete and accurate tracking of every sale. Consent Management: Putting You in Control (For Beetle Tracking Pro) Building trust is key to any successful business. With the ever-changing landscape of data privacy regulations, it’s crucial to ensure you’re collecting user data ethically and transparently. That’s where Beetle Consent comes in (included in Beetle Tracking Pro). This powerful feature makes managing user consent a breeze: Easy-to-customize consent banners: Create clear and user-friendly banners that inform visitors about how their data is used. Granular control: Allow users to choose exactly which data they’re comfortable sharing. Compliance with regulations: Stay ahead of the curve by ensuring your website adheres to data privacy regulations like GDPR and CCPA. With Beetle Consent, you can focus on building relationships with your customers, knowing you’re handling their data responsibly. Why Choose Beetle Tracking? Beetle Tracking is built for webshop owners who care about their customers’ experience and want to ensure that every conversion is accurately tracked. Unlike client-side tracking, our server-side solution works behind the scenes to capture every detail while improving your site’s performance. With just a few clicks, you can unlock the full potential of your tracking, boosting both your insights and your bottom line. Ready to upgrade your tracking? Install Beetle Tracking today and take control of your data like never before. Learn More at beetle-tracking.com External Services This plugin connects to the following external services: Cloudflare Zaraz API Beetle Tracking uses the Cloudflare Zaraz API to send tracking events server-side. When enabled, the plugin sends event data to Cloudflare’s edge network for processing and forwarding to your configured analytics platforms. When data is sent: Event data is transmitted when users interact with your website (page views, add to cart, purchases, etc.) and when you push configuration settings to Cloudflare. What data is sent: Event names, timestamps, page URLs, product information, and user identifiers that you configure in the plugin settings. Service links: – Cloudflare Terms of Service – Cloudflare Privacy Policy – Cloudflare Zaraz Documentation Source Code The JavaScript files in this plugin are compiled from source files using standard WordPress build tools. Build process: – Source files are located in the src/js/ directory – Uses @wordpress/scripts for compilation – Run npm install then npm run build to rebuild from source The full source code is included in the plugin and can be found in the src/ directory.
Voffload for Cloudflare Stream
Voffload for Cloudflare Stream moves the heavy lifting of video hosting and playback off your own server and onto Cloudflare Stream. You pick existing video attachments in your WordPress Media Library, the plugin uploads them to Cloudflare Stream, and your visitors then watch them through Cloudflare’s adaptive‑bitrate player instead of downloading large files from your origin. This is useful if self‑hosted videos are slowing your site down, eating bandwidth, or stressing your host. Cloudflare Stream handles transcoding, multiple quality levels, and global delivery for you. This plugin is an independent project. It is not affiliated with, endorsed by, or sponsored by Cloudflare, Inc. “Cloudflare” and “Cloudflare Stream” are trademarks of Cloudflare, Inc., used here only to describe compatibility. What it does Lists the video attachments already in your Media Library and shows their Cloudflare Stream status (Not uploaded / Processing / Ready / Error). Uploads selected videos to Cloudflare Stream. It first asks Cloudflare to fetch the public file URL (“URL copy”). If Cloudflare cannot reach that URL (for example because of hotlink protection, a firewall rule, or Automatic Platform Optimization), it automatically falls back to a direct upload from your server for files under 200 MB. Stores each video’s Cloudflare Stream UID and processing status on the attachment. Can non-destructively sync existing Cloudflare Stream videos back to matching WordPress video attachments when metadata or a unique exact title/filename match identifies the local attachment. Can delete selected Cloudflare Stream videos from the plugin dashboard, individually or in bulk, while keeping the original WordPress media attachments. Tracks “processing” videos with a background check (WP‑Cron) that runs every 10 minutes — but only while at least one video is still processing. When everything is ready, the background check stops on its own, so the plugin does not make unnecessary calls. Automatically replaces your local video output on the frontend with the Cloudflare Stream player once the matching Stream video is ready (this is optional and can be turned off — see “Automatic replacement” below). Provides a shortcode for manual placement of the player (see the “Shortcode” section below for the exact tag and options). Includes a non‑destructive Connection test that checks your token, account access, and playback settings without uploading anything. Uses a structured dashboard with setup status, workflow descriptions, action guidance, and a small version/copyright/license footer. Never deletes your local video files. Deleting a Stream copy from Cloudflare only clears the plugin’s local Stream metadata; removing local files is intentionally left to you. Do I need a paid Cloudflare account? You need a Cloudflare account and an active Cloudflare Stream subscription. A few clarifications, because this is a common point of confusion: Cloudflare Stream is a separate, usage‑based product. As of 2026 it is billed at roughly $5 per 1,000 minutes of video stored per month and $1 per 1,000 minutes delivered. Encoding and ingest are free, and there are no per‑GB egress fees. You do not need a Cloudflare Pro plan specifically, and Stream does not require the Workers Paid plan. A free Cloudflare account works, as long as you have added a Stream subscription to it. If you are on a Pro or Business plan, Cloudflare includes a small monthly allowance (around 100 minutes of storage and 10,000 minutes of delivery) on top. Always confirm current pricing on Cloudflare’s own pricing page, as it can change. Dashboard guide The plugin dashboard is available under Media → Cloudflare Stream. The top overview explains the three-step workflow: configure Cloudflare, upload or reconnect videos, then serve and maintain the Stream copies. The setup status pills show whether the Account ID, API token, and Customer Code are present before you run actions that need them. The Video Library table lists WordPress video attachments and shows their local file link, Stream status, Stream UID, and shortcode. Upload selected creates a Cloudflare Stream copy for selected local WordPress videos. The WordPress attachment remains in the Media Library. Refresh selected status reads the current processing state from Cloudflare. If no local UID is saved, the plugin first attempts a safe reconnect. Reconnect selected from Cloudflare finds existing Stream videos for selected local attachments by stored metadata first and then by exact unique title/filename matches. Delete from Cloudflare deletes the remote Stream asset after confirmation and clears only local Stream metadata. It does not delete the WordPress attachment. The manual UID fallback is for rare cases where automatic matching is unsafe because Cloudflare metadata is missing or multiple possible matches exist. Compatibility Requires WordPress 6.5 or newer. Tested up to WordPress 7.1. Requires PHP 8.1 or newer. PHP 8.3 or newer is recommended for current WordPress installations. Tested with modern PHP 8.x environments, including PHP 8.5. Getting your Cloudflare details You need three pieces of information from your Cloudflare account. 1. Account ID Log in to the Cloudflare dashboard at https://dash.cloudflare.com/ and open the Stream product (or any account page). Your Account ID is shown in the URL and on the account/overview pages. It is a 32‑character hexadecimal string. 2. API Token (with Stream permission) Create a scoped token so the plugin can upload and check status. Do not use the Global API Key. In the Cloudflare dashboard, go to Manage Account → API Tokens or My Profile → API Tokens and choose Create Token → Create Custom Token. Direct link: https://dash.cloudflare.com/profile/api-tokens Under Permissions, add Account → Stream → Edit. Some Cloudflare screens use the newer label Account → Stream → Write; that is the equivalent write permission. Uploads, status updates, sync/reconnect, and remote deletion require Edit/Write. Read-only tokens can verify access but cannot upload or delete videos. Under Account Resources, scope the token to the specific Cloudflare account that owns the Stream library. Do not add unnecessary permissions. This plugin does not need DNS, Zone, Workers, Cache Purge, or Global API Key permissions. (Recommended) Set an expiration and, if your server has a static IP, restrict the token to that IP. Click Continue to summary → Create Token. Copy the token immediately — Cloudflare shows it only once and you cannot retrieve it later. For better security you can define the token in your wp-config.php instead of saving it in the database: define( 'VOFFLOADCFS_API_TOKEN', 'xxx' ); When this constant is set, the plugin uses it and never stores the token in the WordPress database (so it stays out of database backups). 3. Customer Code This is the code in your Stream playback URLs, of the form customer-CODE.cloudflarestream.com. The plugin needs it to build the official Cloudflare Stream iframe URL. To find it, open Cloudflare Dashboard → Stream → Videos, open any uploaded video, and copy the embed/iframe code. The iframe src contains customer-CODE.cloudflarestream.com. You may paste the bare code, the full customer subdomain, the iframe URL, or the full iframe snippet; the plugin extracts and stores only the code. Automatic replacement (serve from Cloudflare Stream when available) In Media → Cloudflare Stream → Settings you control when ready videos are automatically served from Cloudflare instead of from your server. There are independent checkboxes so you can enable exactly what you want: Automatically replace Gutenberg video blocks — replaces the core/video block on the frontend when the linked attachment has a Stream UID. Automatically replace WordPress [video] shortcodes — replaces the built‑in [video] shortcode output. Automatically replace local video HTML and video‑file links — also catches classic‑editor tags, video blocks that have no attachment ID, and direct links to local video files. Automatic replacement happens only for videos that already have a saved Cloudflare Stream UID and are marked ready. While Cloudflare is still processing a video, the local WordPress video output remains in place. If you turn every automatic option off, nothing on your frontend changes until you place a shortcode yourself. Shortcode Use the shortcode to place a Cloudflare Stream player manually, for example inside a post, page, or widget. By WordPress attachment ID (the ID shown in the Media → Cloudflare Stream table): [voffloadcfs_video id="123"] By Cloudflare Stream UID directly: [voffloadcfs_video uid="VIDEO_UID"] Optional attributes: title — accessible title for the player iframe. aspect — aspect ratio as width/height (default 16/9). Example: aspect="4/3". Example with options: [voffloadcfs_video id="123" title="My talk" aspect="16/9"] The shortcode requires the Customer Code setting to be filled in, because that is what builds the official Cloudflare Stream iframe URL. If a logged‑in editor views a shortcode that cannot render (missing UID, wrong ID, missing Customer Code), the plugin shows a short admin‑only notice explaining why; normal visitors simply see nothing. External services This plugin connects to Cloudflare Stream, a third‑party service operated by Cloudflare, Inc., because that is the service it exists to integrate with. What is sent, and when: When you upload a video: the plugin sends the video (or the public URL of the video so Cloudflare can fetch it), the attachment title, the attachment ID, and your site URL to the Cloudflare API. This happens only when you choose to upload a video. When you check status, run the connection test, reconnect selected videos, or sync existing Stream videos: the plugin sends your Account ID and API token (as an authorization header) to the Cloudflare API to read video status, verify the token, list Stream video metadata, search Stream videos by name for a selected local attachment, or verify a manually entered Stream UID. The connection test, reconnect, and sync do not upload any video. When you delete a Stream video from the plugin dashboard: the plugin sends your Account ID, API token, and the selected Cloudflare Stream video UID to the Cloudflare API. Cloudflare deletes the remote Stream video and its copies. The original WordPress media attachment is not deleted. On the frontend: when a video is served from Stream, the visitor’s browser loads the Cloudflare Stream player iframe from customer-CODE.cloudflarestream.com, so the visitor’s browser communicates directly with Cloudflare. Cloudflare API endpoint: https://api.cloudflare.com/ Cloudflare terms of service: https://www.cloudflare.com/terms/ Cloudflare privacy policy: https://www.cloudflare.com/privacypolicy/ No data is sent anywhere else, and the plugin does not send analytics about your site to the plugin author.
