Nupixl Development Docs
Nupixl Development Docs
  • Introduction
    • Welcome Nupixl
  • Key Mirco Services
    • Pixl Sight
      • Internal Technical Specification & Development Guide
        • Goals & Core Concepts
        • High-Level Architecture
        • User Flow & Key Steps
        • Technical Specifications
        • Role-Based Responsibilities
        • Data Models & Storage
        • Dashboard Interfaces
        • Deployment & Infrastructure
        • Roadmap Phases
  • Prototype Document
    • Prototype Outline
      • Onboarding Experience
      • My Space (Homepage)
      • Teams Page
    • Key Concepts
      • Conversational AI UX/UI
      • Progressive Page Disclosure
      • Context Memory
      • Personal Management System
      • Organizational Management System
      • AI Co-Pilots
        • 1. Pixl Personal (Personas)
        • 2. Team Assistant Pixl
        • 3. Organizational Co-Pilot
        • Briefing System with Pixl Personas
          • Detailed Breakdown of the Briefing System
          • Integration with Team and Organizational Systems
          • Customization and Personalization
          • Privacy and Data Security
        • Integration of AI Co-Pilots in Nupixl’s Workflow
        • Getting Started with AI Co-Pilots
      • Data Flows
      • AI Text Editor
      • Focus Mode
        • 1. Deep Work Mode
        • 2. Collaboration Mode
        • 3. Meeting Mode
        • 4. Learning Mode
        • 5. Personal Time Mode
        • Implementing Focus Modes in Your Workflow
      • Core Apps
        • 1. Nupixl Dashboard
          • Key Features
        • 2. Figma Widget
          • Key Features
      • Core Philosophies
        • Design First Development
        • Seamless Productivity
  • software requirement specifications
    • Specifications
      • 1. Introduction
      • 2. System Overview
      • 3. Functional Requirements
      • 4. Non-Functional Requirements
      • 5. Technology Stack (Initial Proposal)
      • 6. Future Considerations
    • Nupixl Execution Plan
Powered by GitBook
On this page
  • Integration & Architecture Overview
  • 1. Shopify
  • 2. WooCommerce
  • 3. Webflow
  • Billing Integration
  • A/B Testing Framework
  • Conclusion

Was this helpful?

  1. Key Mirco Services
  2. Pixl Sight
  3. Internal Technical Specification & Development Guide

Technical Specifications

Integration & Architecture Overview

This document outlines the integration and architecture across three major platforms: Shopify, WooCommerce, and Webflow.

1. Shopify

  • App Installation: Use OAuth for app installation, capturing permissions such as read_orders and write_script_tags.

  • Traffic Splitting: Implement client-side traffic splitting via script injection.

  • Conversion Tracking: Utilize the orders/create webhook to attribute conversions.

2. WooCommerce

  • Conversion Logging: Employ the orders_created event or plugin-based methods to log conversions.

  • Traffic Management: Use a WordPress plugin for traffic splitting, configurable for both JavaScript and server-side operations.

3. Webflow

  • Design Creation: Supports both manual and AI-based design creation.

  • Site Publishing: Publish to a subdomain (merchant-variant.pixlsight.com).

  • Variant Generation: Use the Webflow API or predefined templates to generate variant sites.

This overview captures essential integration details necessary for building and managing e-commerce platforms across these services.

Billing Integration

Platforms

  • WooCommerce or Standalone: Integrate with Stripe or Normie for subscription or usage billing.

  • Shopify: Implement usage charges.

Billing Types

  • Recurring or Usage-Based:

    • If an uplift is detected (e.g., +$5k sales), Pixl charges a percentage (e.g., 10%).

A/B Testing Framework

Uplift & Revenue Metrics

  • Revenue Calculation: Compare the variant against the control group to measure uplift.

  • Payment & Revenue Sharing: The winning variant triggers a billing event.

Performance Metrics

  • Key Metrics:

    • Conversion rate

    • Bounce rate

    • Load times

    • Repeated visits

Data Collection

  • Visitor Events: Log each visitor's actions with a variant ID.

  • Order Association: Use tags or notes for order alignment.

Traffic Assignment

  • Merchant Control: Define the traffic ratio (e.g., 80% control, 20% variant).

Conclusion

  • Perform comparisons and determine the winning variant through

PreviousUser Flow & Key StepsNextRole-Based Responsibilities

Last updated 1 month ago

Was this helpful?