VISITORTYPE

VisitorType compatibility with REEID Translate

VisitorType compatibility with REEID Translate is being evaluated from available plugin evidence. Dual-mode tracking architecture combining asynchronous browser snippet injection for human engagement metrics and server-side background reporting to capture AI crawlers that do not execute JavaScript. No specific visitor-facing translation surface is currently confirmed.

Visit VisitorType ↗

AWAITING VERIFICATION

What the available evidence establishes for VisitorType.

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
VisitorType is documented in the Analytics category with 5 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 VisitorType 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

  • Dual-mode tracking architecture combining asynchronous browser snippet injection for human engagement metrics and server-side background reporting to capture AI crawlers that do not execute JavaScript.
  • Advanced visitor classification engine that distinguishes between humans, AI crawlers, AI search agents, AI assistants, and agentic browsers using IP-range verification against official vendor lists to flag spoofed bot traffic.
  • Conditional tag firing capability allowing administrators to deploy specific analytics or marketing tags exclusively to identified audience segments, such as serving ad pixels only to verified human visitors.
  • Privacy-first data collection methodology that operates without cookies, stores no visitor IP addresses, strips query strings before storage, and automatically honors Global Privacy Control (GPC) and Do Not Track (DNT) signals.
  • Cross-platform attribution analysis that identifies referral sources from major AI interfaces like ChatGPT, Perplexity, and Gemini, including detection of visits often misclassified as direct traffic in standard analytics tools.

CONTENT BOUNDARY

VisitorType 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

VisitorType and REEID Translate FAQ.

What does VisitorType do according to the available plugin evidence?

VisitorType has 5 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 VisitorType?

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

What would establish translation scope for VisitorType?

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 VisitorType in a multilingual WordPress workflow.

REEID documents VisitorType 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