PUSHAI

PushAI – Self-Hosted Web Push Notifications compatibility with REEID Translate

PushAI – Self-Hosted Web Push Notifications compatibility with REEID Translate is being evaluated from available plugin evidence. Self-hosted Web Push delivery using the native Web Push protocol and site-owned VAPID credentials (generated automatically on activation). No specific visitor-facing translation surface is currently confirmed.

Visit PushAI – Self-Hosted Web Push Notifications ↗

AWAITING VERIFICATION

What the available evidence establishes for PushAI – Self-Hosted Web Push Notifications.

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
PushAI – Self-Hosted Web Push Notifications 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 PushAI – Self-Hosted Web Push Notifications 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

  • Self-hosted Web Push delivery using the native Web Push protocol and site-owned VAPID credentials (generated automatically on activation).
  • Opt-in subscription UX via a `[pushai_button]` shortcode and an optional customizable permission popup.
  • Automatic notification generation for new posts and custom post types, plus a manual notification composer.
  • Click tracking with automatic UTM parameter tagging on push links, with a filter to customize or disable UTM parameters.
  • Per-user targeting for notifications using `target_user_id` / `target_user_ids`, with metadata fields (`source_type`, `source_id`) used for UTM campaign construction rather than recipient selection.
  • Device-aware subscription handling that keeps separate active subscriptions per device type (mobile vs desktop) and prunes stale/duplicate subscriptions.
  • Delivery lifecycle tracking including delivery history/status and a background delivery queue with retries; exposes developer hooks for queued/failed/completed events.

CONTENT BOUNDARY

PushAI – Self-Hosted Web Push Notifications 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

PushAI – Self-Hosted Web Push Notifications and REEID Translate FAQ.

What does PushAI – Self-Hosted Web Push Notifications do according to the available plugin evidence?

PushAI – Self-Hosted Web Push Notifications 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 PushAI – Self-Hosted Web Push Notifications?

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

What would establish translation scope for PushAI – Self-Hosted Web Push Notifications?

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 PushAI – Self-Hosted Web Push Notifications in a multilingual WordPress workflow.

REEID documents PushAI – Self-Hosted Web Push Notifications 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