Use when adding tracking code, advertising pixels, third-party integrations, popups, banners, or client-side JavaScript to sites. Triggers include embed, inject, script, third-party integration, DOM injection, Google Analytics, Facebook Pixel, tracking pixel, chat widget, popup, coupon popup, custom JavaScript, site script.
Installation
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Use when adding tracking code, advertising pixels, third-party integrations, popups, banners, or client-side JavaScript to sites. Triggers include embed, inject, script, third-party integration, DOM injection, Google Analytics, Facebook Pixel, tracking pixel, chat widget, popup, coupon popup, custom JavaScript, site script.
compatibility
Requires Wix CLI development environment.
Wix Embedded Script Builder
Creates embedded script extensions for Wix CLI applications. Embedded scripts are HTML code fragments that get injected into the DOM of Wix sites, enabling integration with third-party services, analytics tracking, advertising, and custom JavaScript functionality.
Quick Start Checklist
Follow these steps in order when creating an embedded script:
Embedded scripts must declare a type for consent management:
Type
Description
Use Cases
ESSENTIAL
Core functionality crucial to site operation
Authentication, security features
FUNCTIONAL
Remembers user choices to improve experience
Language preferences, UI customization
ANALYTICS
Provides statistics on how visitors use the site
Google Analytics, Hotjar, Mixpanel
ADVERTISING
Provides visitor data for marketing purposes
Facebook Pixel, Google Ads, retargeting
Selection rule: If a script falls into multiple types, choose the option closest to the bottom of the list (most restrictive). For example, a script with both Analytics and Advertising aspects should be typed as ADVERTISING.
Placement Options
Placement
Description
Best For
HEAD
Between <head> and </head> tags
Analytics, early initialization
BODY_START
Immediately after opening <body> tag
Critical functionality, noscript
BODY_END
Immediately before closing </body> tag
Non-blocking scripts, performance
Selection guidelines:
Analytics/tracking → HEAD (initialize early)
Advertising pixels → BODY_END (non-blocking)
Critical functionality → HEAD or BODY_START
Non-critical features → BODY_END (better performance)
Dynamic Parameters and Dashboard Configuration
Every embedded script requires a companion dashboard page to configure its parameters. Site owners use the dashboard page UI to set values, which are then passed to the embedded script as template variables.
Architecture Flow
Dashboard Page (React UI)
│
│ embeddedScripts.embedScript({ parameters: {...} })
▼
Wix App Management API
│
│ Stores parameters, injects as template variables
▼
Embedded Script (HTML)
│
│ {{parameterKey}} → actual value
▼
Site DOM
Related skill: Use wix-cli-dashboard-page to create the configuration UI for your embedded script.
Parameter Types
Type
Description
Dashboard Component
TEXT
Single-line text
Input
NUMBER
Numeric value
Input type="number"
BOOLEAN
True/false toggle
ToggleSwitch, Checkbox
IMAGE
Image from media manager
ImagePicker
DATE
Date only
DatePicker
DATETIME
Date with time
DatePicker + TimeInput
URL
URL with validation
Input
SELECT
Dropdown options
Dropdown
COLOR
Color value
ColorPicker
Template Variable Syntax
Embedded scripts support parameterization using template variable syntax {{variableName}}. These parameters are configured through the dashboard and passed as template variables that should be used in your HTML/JavaScript code.
Usage Instructions:
Template Variable Syntax:
Use {{parameterKey}} syntax to insert parameter values into your HTML
Template variables work in HTML attributes
They will be replaced with actual values when the script is injected
HTML Attributes (REQUIRED):
Store ALL parameter values in data attributes on a configuration element
Template variables can ONLY be used here, not directly in JavaScript
Note: The dashboard page requires its own extensions.ts file. Without this file, the dashboard page will not appear in the Wix dashboard.
WARNING: The dashboard page uses DIFFERENT field names than embedded scripts:
Dashboard pages use title, routePath, component
Embedded scripts use name, source, placement, scriptType
Do NOT apply embedded script field names to dashboard page registrations.
See wix-cli-dashboard-page skill for dashboard page implementation details and the extension registration pattern.
Implementation Pattern
<!-- Configuration element with template variables --><divid="my-config"data-api-key="{{apiKey}}"data-enabled="{{enabled}}"></div><!-- Container for dynamic content --><divid="my-container"></div><style>/* Scoped styles for the embedded content */#my-container {
/* styles */
}
</style><scripttype="module">// Get configuration from data attributesconst config = document.getElementById("my-config");
if (!config) thrownewError("Config element not found");
const { apiKey, enabled } = config.dataset;
// Exit early if disabled (use throw at module scope, not return)if (enabled !== "true") {
thrownewError("Script disabled");
}
// Implement functionality in a named function (return is allowed here)asyncfunctioninitialize() {
try {
// Your implementation
} catch (error) {
console.error("Script error:", error);
}
}
// Initialize when DOM is readyif (document.readyState === "loading") {
document.addEventListener("DOMContentLoaded", initialize);
} else {
initialize();
}
</script>
Examples
Analytics Tracking
Request: "Add Google Analytics tracking to my site"
Implements: Intercom SDK initialization, user identification
Best Practices
Always create a dashboard page: Every embedded script needs a configuration UI
Include enable/disable toggle: Let site owners control activation without removing the script
Performance: Minimize impact - scripts should be lightweight and non-blocking
Security: Avoid inline event handlers, validate data, escape user input
Error handling: Fail silently when appropriate - don't break the site
Module scope early exits: Use throw new Error() for early exits at module scope, not return. Rollup (used by Astro) doesn't allow return statements at module scope. Wrap main logic in a named async function where return is valid.
Type conversions: Parameters are always strings - convert in JavaScript as needed
API calls: Only create fetch() calls to /api/* endpoints that exist in the API spec
Scoping: Prefix CSS classes and IDs to avoid conflicts with site styles
Cleanup: Remove event listeners and intervals when appropriate
Complete Example: Coupon Popup
1. Define Parameters
Parameters for "cart-coupon-popup":
- couponCode (TEXT, required) - The coupon code to display
- popupHeadline (TEXT, required) - Headline text
- popupDescription (TEXT, required) - Description text
- minimumCartValue (NUMBER) - Minimum cart value to show popup
- enablePopup (BOOLEAN, required) - Enable/disable toggle
2. Embedded Script (embedded.html)
<divid="popup-config"data-coupon-code="{{couponCode}}"data-popup-headline="{{popupHeadline}}"data-minimum-cart-value="{{minimumCartValue}}"data-enable-popup="{{enablePopup}}"
></div><divid="popup-container"></div><scripttype="module">// Get configuration from data attributesconst config = document.getElementById("popup-config");
if (!config) thrownewError("Config element not found");
const { couponCode, popupHeadline, minimumCartValue, enablePopup } =
config.dataset;
// Exit early if disabled (use throw at module scope, not return)if (enablePopup !== "true") {
thrownewError("Popup disabled");
}
// Main logic in a function (return is allowed here)asyncfunctioninitializePopup() {
const minValue = Number(minimumCartValue) || 0;
// ... popup implementation
}
// Initialize when DOM is readyif (document.readyState === "loading") {
document.addEventListener("DOMContentLoaded", initializePopup);
} else {
initializePopup();
}
</script>
3. Dashboard Page (See wix-cli-dashboard-page skill)
Uses embeddedScripts API from @wix/app-management:
import { embeddedScripts } from"@wix/app-management";
// Load parametersconst script = await embeddedScripts.getEmbeddedScript();
const params = script.parameters; // { couponCode: "...", ... }// Save parameters (all values must be strings)await embeddedScripts.embedScript({
parameters: {
couponCode: "SAVE20",
minimumCartValue: "50", // Number as stringenablePopup: "true", // Boolean as string
},
});
Extension Registration
Extension registration is MANDATORY and has TWO required steps.
Step 1: Create Script-Specific Extension File
Each embedded script requires an extensions.ts file in its folder:
The id must be a unique, static UUID v4 string. Generate a fresh UUID for each extension - do NOT use randomUUID() or copy UUIDs from examples. Replace {{GENERATE_UUID}} with a freshly generated UUID like "a1b2c3d4-e5f6-7890-abcd-ef1234567890".
Property
Type
Description
id
string
Unique static UUID v4 (generate fresh)
name
string
Display name for the script
source
string
Relative path to the HTML file
placement
enum
HEAD, BODY_START, or BODY_END
scriptType
enum
ESSENTIAL, FUNCTIONAL, ANALYTICS, ADVERTISING
Step 2: Register in Main Extensions File
CRITICAL: After creating the script-specific extension file, you MUST read wix-cli-extension-registration and follow the "App Registration" section to update src/extensions.ts.
Without completing Step 2, the embedded script will not be deployed to the site.
Enable Embedded Script Permission
After implementation, the app developer must manually enable the embedded script permission:
