BIG-FLYTX BY MAS

BIG-FLYTX by MAS compatibility with REEID Translate

BIG-FLYTX by MAS compatibility with REEID Translate is being evaluated from available plugin evidence. Paused-by-default installation/activation: does not collect or transmit visitor events until an administrator explicitly authorizes tracking and enables the plugin in settings. No specific visitor-facing translation surface is currently confirmed.

Visit BIG-FLYTX by MAS ↗

AWAITING VERIFICATION

What the available evidence establishes for BIG-FLYTX by MAS.

Official plugin information supports the compatibility context documented for this category.

AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.

PLUGIN PROFILE
BIG-FLYTX by MAS is documented in the Analytics category with 7 concrete capabilities identified in the current evidence.

EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.

COMPATIBILITY REVIEW

How BIG-FLYTX by MAS compatibility is evaluated

01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.

02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.

03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.

04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.

PLUGIN INTELLIGENCE

What the official plugin evidence shows

Plugin capabilities

  • Paused-by-default installation/activation: does not collect or transmit visitor events until an administrator explicitly authorizes tracking and enables the plugin in settings.
  • Consent gating options: supports Site-owner managed mode (site owner handles consent/notice via site policy/CMP) and Strict visitor gate mode that waits for a `bftx_consent=granted` cookie or the `bftx_mas_tracking_consent_granted` filter before collection/transmission.
  • Multi-destination conversion tracking with selectable delivery modes: can route enabled events to browser pixels, a Google Tag Manager dataLayer-only mode, and/or server-side event delivery (including monitor-only and server-only modes).
  • Server-side tracking with deduplication controls: supports browser, dataLayer-only, server-only, or monitor-only modes and includes event IDs/mapping controls to reduce duplicate conversion delivery when other tracking tools are active.
  • WooCommerce conversion analytics: tracks WooCommerce product views, add-to-cart, checkout activity, purchases, order values, customer totals, and revenue while preserving HPOS and Cart/Checkout Blocks compatibility.
  • Frontend script loading and server requests are conditional: provider browser scripts are loaded only after explicit administrator authorization/configuration (and after consent in Strict visitor gate mode); server-side conversion requests are sent only when the relevant destination toggles and credentials are configured.
  • Privacy/data handling controls: stores first-party event data in plugin-owned tables; can collect visitor IDs/URLs/referrers/UTM/ad click IDs and hashed identifiers; raw name/email/phone storage is disabled by default and can be enabled only when permitted by the site’s privacy policy/consent process; supports Do Not Track support and configurable retention/log retention.

CONTENT BOUNDARY

BIG-FLYTX by MAS capabilities and translation scope are documented separately.

The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.

Functional capability alone is not treated as evidence that a value should be translated.

LIMITATIONS & QA

Verification notes

  • This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.

COMMON QUESTIONS

BIG-FLYTX by MAS and REEID Translate FAQ.

What does BIG-FLYTX by MAS do according to the available plugin evidence?

BIG-FLYTX by MAS has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.

Is a REEID translation surface currently confirmed for BIG-FLYTX by MAS?

No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.

What would establish translation scope for BIG-FLYTX by MAS?

The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.

RELATED GUIDES

Continue through the compatibility library.

INTEGRATION EVIDENCE

Evaluate BIG-FLYTX by MAS in a multilingual WordPress workflow.

REEID documents BIG-FLYTX by MAS functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.

Translation scope will be published when concrete visitor-facing content is established by evidence.

Shopping Cart
Scroll to Top