BIG-FLYTX by MAS
| 开发者 | makeanythingsimple |
|---|---|
| 更新时间 | 2026年7月13日 17:02 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
BIG-FLYTX by MAS is a WordPress and WooCommerce conversion tracking plugin for GA4, Meta Pixel, Google Tag Manager dataLayer, advertising pixels, leads, purchases, and optional server-side event delivery.
Track first-party visitors, customer journeys, form leads, WooCommerce add-to-cart and purchase events from one dashboard. BIG-FLYTX supports browser tracking, dataLayer-only mode, server-side tracking, event deduplication, consent controls, and customer intelligence.
WordPress Conversion Tracking
Capture normalized page, lead, ecommerce, and conversion events without editing theme files. The plugin stores first-party event data in plugin-owned tables and can route enabled events to dataLayer, browser pixels, or configured server endpoints.
WooCommerce Analytics and Purchase Tracking
Track WooCommerce product views, add-to-cart actions, checkout activity, purchases, order values, customer totals, and revenue while preserving HPOS and Cart/Checkout Blocks compatibility.
Meta Pixel, GA4, and Google Tag Manager
Configure Meta Pixel and Conversions API, Google Analytics 4, Google Ads, Google Tag Manager dataLayer, Microsoft Ads UET, TikTok, LinkedIn, Pinterest, Snapchat, X, Reddit, Quora, Telegram, and custom relays.
Server-side Tracking and Event Deduplication
Use browser, dataLayer-only, server-only, or monitor-only modes. Event IDs and mapping controls help reduce duplicate conversion delivery when other tracking tools are active.
Privacy and Consent Controls
By default, the plugin is installed in paused mode. A site administrator must review the disclosures, explicitly authorize tracking, enable BIG-FLYTX, and enable each desired destination. No visitor event is collected or transmitted merely by installing or activating the plugin.
安装:
- Upload the plugin ZIP through Plugins > Add New > Upload Plugin.
- Activate BIG-FLYTX by MAS.
- Go to BIG-FLYTX > Settings.
- Review Privacy, Compliance & Data Retention settings.
- Enable only the tracking sources you need.
- Add Pixel IDs, Measurement IDs, API tokens, and endpoint details where required.
- Test events before using the plugin on a production client site.
屏幕截图:
常见问题:
What tracking mode should I use?
Use Full Tracking when no other tracking plugin controls pixels. Use dataLayer Only when Google Tag Manager controls tags. Use Server Only when browser pixels are already installed elsewhere but BIG-FLYTX should send server events. Use Monitor Only for safe testing and event database logging without sending to ad platforms.
Does it send server-side events automatically?
No. Server-side events are sent only when Global Server Tracking and the specific destination server toggle are enabled and credentials are configured. Otherwise the plugin uses browser/dataLayer tracking only.
Does it track immediately after activation?
No. The plugin is paused by default. A site administrator must enable it from the settings screen.
Does it edit theme or plugin files?
No. It uses WordPress hooks, WooCommerce hooks, browser detection, REST endpoints, and plugin-owned database tables.
Does it store personal data?
It can store name, email and phone when forms or orders provide them, but raw PII storage is disabled by default. Site owners can enable raw storage or keep hashed values only where possible.
Does it require a BIG-FLYTX consent cookie?
Not in Site-owner managed mode. In that mode, the administrator explicitly authorizes the plugin and manages any required visitor notice or consent through the website's own privacy process or CMP. Strict visitor gate mode is also available and waits for bftx_consent=granted or the bftx_mas_tracking_consent_granted filter.
Does BIG-FLYTX support WooCommerce conversion tracking?
Yes. It can capture WooCommerce product, cart, checkout, purchase, order-value, customer, and revenue events through WooCommerce APIs, including HPOS-compatible order access.
Can I use Meta Pixel and Meta Conversions API together?
Yes. You can enable browser and server delivery together and use shared event IDs for deduplication, provided the required Meta credentials are configured.
Can BIG-FLYTX send GA4 ecommerce events?
Yes. GA4 browser measurement and optional Measurement Protocol delivery can be configured for normalized ecommerce and conversion events.
Can I use Google Tag Manager dataLayer-only mode?
Yes. Choose dataLayer Only when GTM should control the final tags and BIG-FLYTX should only publish normalized event payloads.
Can it track form leads and customer journeys?
Yes. Supported form and builder integrations can capture lead events, and the dashboard can connect first-party visitor, lead, customer, and ecommerce activity.
Does uninstall delete data?
Only if you enable "Delete BIG-FLYTX Tables on Uninstall" before uninstalling.
更新日志:
1.1.2
- Prevented notices from other plugins from being injected inside the BIG-FLYTX branded header.
- Added a standard accessible WordPress page heading outside the visual header for compatibility with third-party notice scripts.
- Added a JavaScript safety fallback that relocates dynamically inserted notices above the BIG-FLYTX header.
- Preserved all tracking, privacy, integration, and stored-data behavior.
- Fixed a PHP 8.1+ admin deprecation warning after activation and on hidden utility pages.
- Registered Setup Wizard and utility screens under the BIG-FLYTX parent so WordPress always receives a valid page title.
- Kept utility screens hidden from the normal menu and preserved all UI 2.0 tracking behavior.
- Introduced BIG-FLYTX UI 2.0 with a branded Overview dashboard and tracking health score.
- Replaced horizontal settings tabs with a searchable left settings sidebar.
- Replaced binary enabled/disabled dropdowns with accessible toggle switches.
- Added visual integration status cards and a guided first-time setup wizard.
- Added an improved sticky save bar, activity view, reports hub, and downloadable redacted diagnostics.
- Preserved existing tracking, event, privacy, delivery, and integration behavior.
- Added WordPress.org plugin icons, responsive banners, and eleven product screenshots.
- Improved search-focused tags, short description, feature headings, FAQ content, and screenshot captions.
- Updated the bundled documentation and release metadata for easier monthly maintenance.
- No automatic tracking behavior was enabled or changed; the plugin remains paused by default.
- Replaced the mandatory plugin-specific visitor cookie with explicit administrator opt-in authorization.
- Added two visitor-consent modes: site-owner managed and optional strict cookie/filter gating.
- Kept all tracking paused by default and blocked external delivery until the administrator accepts the data-sharing disclosure.
- Updated REST authorization and privacy documentation to follow the selected consent mode.
- Made explicit visitor consent mandatory for every tracking mode.
- Replaced raw PHP-rendered script tags with WordPress script registration, enqueue, localization, and inline-script APIs.
- Restricted the REST health endpoint to administrators with the
manage_optionscapability. - Added complete external-service disclosures with data-use, terms, and privacy links.
- Added a human-readable JavaScript source counterpart and documented the no-build source process.
- Final live-data stability pass for CRM/customer import.
- Live Data Sync can enable raw CRM fields and optionally rebuild BIG-FLYTX Customers/Leads before reimport.
- Dashboard Purchases and Revenue now include synced historical WooCommerce customer totals, not only newly tracked Purchase events.
- Customer LTV and event values are formatted to two decimal places in admin tables.
- Customer upsert now preserves existing CRM fields and avoids overwriting raw name/email/phone with blank data.
- WooCommerce customer aggregation now uses WooCommerce order APIs for better HPOS/custom order table compatibility.
- Added WooCommerce total-value payload improvements for orders and carts, including order total, subtotal, discounts, coupon codes, tax, shipping, shipping tax, fees and additional charges.
- Added cleaner production event controls for low-value browser events, scroll events, generic button clicks, FormStart, and browser Lead fallback.
- Throttled SessionStart and Search browser detection to reduce live-site noise from repeated page loads or search forms.
- Reduced false Lead events from checkout/search/builder forms and stopped generic builder/theme clicks unless low-value event tracking is enabled.
- Kept WooCommerce AddToCart/RemoveFromCart improvements from v1.0.13.
- Added a Duplicate Event Check admin page to show exact duplicate IDs, repeated order events, browser Purchase fallback issues, rapid repeated events, and noisy Search/Scroll/FormStart/ClickButton patterns.
- Added Duplicate Check quick link in Tools and a sidebar submenu for easier QA before enabling production ad delivery.
- Added Tracking Mode options: Full Tracking, dataLayer Only, Server Only, and Monitor Only.
- Added safer duplicate-tracking detection and recommendations for sites already using GTM, Site Kit, PixelYourSite, Facebook for WooCommerce, TikTok, Pinterest, Bing/Microsoft, or header-script tracking plugins.
- Updated settings, dashboard, Health Check, and frontend delivery logic to respect the selected tracking mode.
- Improved settings UI with user-friendly tabs for core tracking, privacy, event mapping, Meta, Google/Bing, social sources, commerce, forms/builders, themes, server/license and tools.
- Added an enqueued admin JavaScript file for tab switching and improved admin CSS layout.
- Fixed Plugin Check output escaping error in Meta Pixel initialization.
- Added a version parameter to the Google gtag enqueue call.
- Fixed SQL identifier handling, privacy queries, uninstall cleanup, export handling, script enqueue handling, and readme tags for Plugin Check review.
- Improved CSV export SQL handling by using WordPress identifier placeholders for plugin-owned table names.
- Bumped minimum WordPress version to 6.2 for safe identifier placeholder support.
- Updated WordPress.org submission metadata and Tested up to value.
- Changed default activation posture to paused until the administrator enables tracking.
- Changed raw PII storage default to disabled.
- Improved privacy and external service disclosures in readme.txt.
- Improved small sanitization/escaping details around admin notices and CSV export filenames.
- Added GPL/readme/uninstall/privacy hardening.
- Added privacy-policy disclosure content.
- Added WordPress personal-data exporter and eraser support.
- Added consent-gating and Do Not Track settings.
- Added raw PII storage toggle and admin PII masking.
- Added retention cleanup cron for events/visitors/deliveries.
- Added safer uninstall routine controlled by plugin setting.
- Added standard/recommended event mappings for LinkedIn, Pinterest, Snapchat, X/Twitter, Reddit, Quora and Microsoft/Bing.
- Added GA4 and TikTok event libraries and normalized event mapping.