- How do I install goldnead/statamic-affiliates in a Laravel Statamic project?
- Install it with Composer using the package name goldnead/statamic-affiliates, then complete the Statamic addon setup in your control panel. The package is built for Laravel-powered Statamic sites and adds affiliate, referral link, commission, and payout workflows. The v0.2.1 release is drop-in with no migration and no new config key, but you should still check the package composer.json for the supported Statamic and Laravel constraints.
- Which Statamic and Laravel versions does Statamic Affiliates support?
- The provided release details do not list exact Statamic or Laravel version constraints, so treat composer.json as the source of truth before upgrading. The v0.2.1 navigation change is version-gated on statamic-brand-context 1.16 or higher. Below that version, the addon ignores settingsNavParent() and keeps its previous control-panel layout.
- How does goldnead/statamic-affiliates attribute referrals and conversions?
- Attribution comes from statamic-payments events, not from a request field such as a query parameter. The addon uses tracking links with a consent-aware cookie for partner referral visits. That event-based design is important because it avoids letting arbitrary request data claim a conversion.
- What commission types can affiliates earn in this Statamic affiliate addon?
- Commissions are configured per offer and can cover first payments, recurring payments, bumps, and upsells. Each offer can therefore have its own earning rules while still using the same partner and tracking-link workflow. Refunds can reverse those commissions, and a hold period controls when they become payable.
- How do refunds, hold periods, and payouts work for affiliate commissions?
- Refunds reverse the affected commissions instead of leaving them payable. A hold period gives you time to process refunds or cancellations before commissions are released. Payout lists then let you manage what partners are owed from the control panel.
- Can Statamic Affiliates handle joint-venture revenue splits and partner coupons?
- Yes, the package overview describes joint-venture revenue splits and coupons that belong to a partner. Those features fit partner programmes where revenue is shared or where a coupon should be attributed to a specific affiliate. You should still test the exact split and coupon rules against your offer and payment flow before going live.
- What does settingsNavParent() do in statamic-affiliates v0.2.1?
- settingsNavParent() returns a [section, name] tuple that tells the Statamic control panel where the addon's settings should appear. The addon declares intent, while the host integration, such as statamic-brand-context, decides placement. Because the package is still 0.x, treat the method signature and tuple shape as unstable until a 1.0 release.
- Do I need statamic-brand-context 1.16 for the new Statamic Affiliates settings navigation?
- The new nested settings placement is activated when statamic-brand-context 1.16 or higher is present. Older versions ignore settingsNavParent() and preserve the prior layout, so no migration or config edit is required. Mixed-version environments can show inconsistent control-panel placement until brand-context is aligned.
- How should I test affiliate tracking, commissions, and refunds before production?
- Use a staging Statamic environment with your real statamic-payments event flow and consent-aware cookie behavior. Create test partners, tracking links, offers, first payments, recurring payments, bumps, upsells, refunds, hold periods, payout lists, joint-venture splits, and partner coupons. If you run different statamic-brand-context versions, verify both the sub-item and shared Addon-Suite settings layouts to catch navigation differences.
- Is goldnead/statamic-affiliates production-ready, and what maintenance risks should I consider?
- The addon is at 0.x, so the settingsNavParent() contract and other APIs may change before 1.0; pin versions and re-review on minor upgrades. Two control-panel layouts can exist depending on statamic-brand-context versions, and overlapping [section, name] declarations across addons may create navigation collisions. For production, stage the upgrade, document both layouts, and compare alternatives on event-based attribution, refund reversal, hold periods, and payout support rather than only link tracking.