| 开发者 | alexstandiford |
|---|---|
| 更新时间 | 2026年7月10日 22:55 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Navigate to Siren in your WordPress admin menu and click "Add Program." Choose your commission structure, set the rules for how partners earn rewards, and publish. Partners can sign up through a registration form or be added manually.
Yes. Create as many programs as you need, each with its own commission rates, attribution rules, and eligible partners.
Yes. Siren integrates deeply with WooCommerce, including automatic order tracking, product-based commissions, coupon attribution, and full WooCommerce Subscriptions support for recurring commissions.
Yes. When a WooCommerce subscription renews, Siren can trigger a new conversion and award commissions to the attributed partner. Initial payments, renewals, plan changes, and refund adjustments are all tracked.
Siren's term for any partner who earns rewards through your programs: affiliates, content creators, agency partners, resellers, and more.
Siren supports shared engagement pools that split rewards evenly, performance-weighted pools that distribute proportionally to contribution, and top-score-wins where a single partner takes the full reward.
Visitor tracking records a lightweight engagement event; commission calculation and attribution run in background jobs via Action Scheduler rather than during page loads.
Yes. Siren includes a partner dashboard where collaborators can log in to view their earnings, track referrals, and see payment status. They do not need WordPress admin access.
Siren's Payout Manager lets you send rewards directly to partners. Approved commissions are compiled into payout records that you can fulfill through PayPal, bank transfer, or other methods.
Yes. Siren Lite is free and runs a complete WooCommerce affiliate program — unlimited affiliates, link and coupon tracking, automatic commission calculation, and a partner dashboard. Twelve of the built-in starter recipes work on the free tier. Paid tiers add scheduled distributions, overrides, and additional program types.
Siren is built for non-developers. Pick a starter recipe such as the Basic Affiliate Program, apply it in a few clicks, and you have a working program with sensible defaults. No code, no separate SaaS account, and no per-affiliate fees.
Where a traditional affiliate plugin credits a single affiliate per sale, Siren can run multiple programs at once and split credit across every partner who contributed, using the attribution model you choose per program. It also covers referral, partner, creator, sales-commission, lead-generation, and loyalty programs from the same plugin.
Yes. Siren supports tiered programs where senior partners earn an override on the sales their recruits refer, VIP and standard rate tiers, and manager overrides for sales teams. You define the reporting lines and the rates.
Yes. Siren integrates with Easy Digital Downloads for affiliate and partner programs built around digital products, licenses, and recurring revenue, including coupon attribution and per-product commission rates.
Yes. Siren works with LearnDash and LifterLMS, so you can pay affiliates for course sales, share course revenue with instructors, and run instructor royalty or revenue-share programs from inside your LMS.
Yes. Each collaborator can be assigned a unique coupon code, and Siren credits the sale whenever that code is used at checkout — no link click required. This is ideal for influencers who share codes on Instagram, TikTok, or YouTube.
Yes. Siren's referral programs give each customer a unique link or code and reward them, often in store credit, when a friend they refer makes a purchase. You can also run flat-bounty B2B referral programs.
No. WooCommerce is the deepest integration, but Siren also works with Easy Digital Downloads, North Commerce, LearnDash, LifterLMS, and form plugins like Gravity Forms and Ninja Forms — so you can track sales, course enrollments, or lead submissions.
RecipeImportJobExecutor replaces RecipeImportTaskHandlerRepairJobExecutor — generic executor that looks up any registered RepairAction by subtypeRunDebugRepair switches from sync-inline to async-dispatch (returns 202 + jobId, 409 when a matching repair is already in flight)DebugTab RepairDialog dispatches async, swaps to a polling view with queued/running/complete statesRecipeImportJob model/datastore/table/task/service/installer all deletedincentiveArgs, autoApprove, expirationDays, activeConversionTypes, lineItemFiltersdistributionArgs/poolResolverArgs per-distributor (fixes parallel-importer clobbering), concrete schedule shape, engagementTypes, transactionCompilers, lineItemFiltersaliases (typed, with issuedDate for migration link continuity) and bindings (collaborator→program, collaborator→distributor)active_pluginsSetupCollaboratorPortal enqueued the Vite-built portal bundle without type="module". 37 shared chunks + main entry all threw Cannot use import statement outside a module; the SPA stalled at "Loading…" forever. Filter added on script_loader_tag that marks every portal handle as a module at tag-render time. RegisterCollaboratorPortalBlock already did this for the editor-preview path; this brings the frontend portal enqueue path in line.bin/seed-screenshot-data.php was writing to a non-existent totalCount column (actual column is count), silently dropping all activity data. Also fixes activity-type enum to match STRATEGY_TO_ACTIVITY_TYPE (site_visit, content_view, product_sale, form_submission, coupon_use) and seeds per-day periods so the last-6-months activity chart has a real time series.:root { --background/--foreground/--primary/--accent: ...; } overrides generated from block attrs were attached to siren-collaborator-portal-inline and enqueued before the Vite-built Tailwind bundles. The bundles carry their own :root defaults, so they printed last and won the cascade — the editor preview updated but the public portal rendered stock colors. Moved override emission to after the bundle loop, attached via wp_add_inline_style() to the last bundle handle so our rule is last in source order.TextControl asking for a pasted URL. Replaced with MediaUpload + MediaUploadCheck — WordPress's native media modal, URL-based storage preserved for backward compat, thumbnail preview + Replace / Remove controls.build/blocks/ output isn't wired into bin/build.php or .github/workflows/release.yml. Release workflow runs frontend:build:all but never wp-scripts build, and the build script doesn't relocate ./build/ into lib/LiteApplication/build/ where the path resolver expects it. Every essentials install will hit this in the block editor until it's fixed. Not blocking 3.2.0 — block works at runtime, only the editor is affected.job_schedules table + cron dispatcher for recurring jobs (telemetry, nightly prunes) — framework designed for it, not built.