Statamic Lead Magnets Laravel Package

Product Decisions This Supports

• Lead magnet and gated-content strategy: The package now supports delivery of a product or access entitlement on a reader’s account, not only a file download. This helps PMs test whether a lead magnet should drive account creation, course enrollment, or product activation rather than a one-off download.
• Product-led onboarding and entitlement flows: The new Access delivery method, backed by Contracts\AccessSubjectResolver, lets the host decide how to find or create the reader account and issue a sign-in link. The addon does not create users, so account ownership, identity, and provisioning remain product/engineering decisions.
• Build vs. buy for delivery mechanics: Teams can avoid rebuilding confirmation mail, delivery templates, signed download links, and request-notice plumbing. PMs can prioritize differentiation in the offer, landing experience, and lifecycle messaging instead of delivery infrastructure.
• Lifecycle messaging roadmap: Mail series support lets the first delivery mail be replaced by the first mail in an automation series for first-time readers, with fallback behavior when automations are absent or already applied. This is useful for onboarding, nurture, and activation experiments.
• Personalization without core forks: The DeliveryVariables event lets engineering add mail placeholders from a listener without subclassing DeliveryService. PMs can request richer confirmation and delivery messages without committing to a custom delivery implementation.
• Operational visibility: The optional notifications.webhook_url posts every request to a Discord-compatible webhook, supporting lead-monitoring and support workflows for launches, campaigns, or high-value downloads.
• Security/UX edge-case planning: Signed download links for access resources returning 404 is a behavior PMs should account for in support flows, expectation setting, and content-access troubleshooting.

When to Consider This Package

Consider this package when:

• The product is built on Laravel/PHP and needs lead-magnet delivery, gated content, file delivery, or access-based entitlement delivery without a large custom build.
• The team wants configurable delivery methods, templated confirmation/delivery mail, and a migration path that is additive rather than disruptive. The v3.12.0 migration adds nullable fields only, so existing resources do not change.
• The roadmap includes access products, course/material enrollment, or account-based fulfillment, and the host can own account lookup/creation and sign-in-link generation.
• The team already uses, or may later add, an automations addon for mail series, and wants graceful fallback when automations are unavailable, disabled, or already triggered for a reader.
• Engineering values extension points such as DeliveryVariables and AccessSubjectResolver over patching package internals.
• Launch or growth operations would benefit from lightweight request notifications via a Discord-compatible webhook.

Look elsewhere when:

• The stack is not Laravel/PHP or the team expects a framework-agnostic marketing suite.
• The product needs full CRM, user provisioning, complex segmentation, or a complete marketing-automation platform. This package supports delivery and integration seams; it does not replace the host’s identity or automation systems.
• Account creation, authentication, and entitlement ownership cannot be handled by the host application.
• The team requires mail-series behavior without any automations addon and cannot accept fallback to the standard delivery mail.
• The delivery experience depends heavily on custom access UX not covered by product slug, landing path, and {{ access_url }} placeholders.

How to Pitch It (Stakeholders)

• For executives: v3.12.0 extends the package from file-based lead delivery into account-based access delivery, making it more useful for courses, materials, and product onboarding. It reduces custom build for delivery mail, access links, lifecycle messaging hooks, and operational notices while leaving user creation and entitlement strategy with the host product.
• For engineering: The release is additive and low-risk to adopt: one nullable migration, optional config, a host-bound AccessSubjectResolver, a DeliveryVariables event for mail placeholders, and optional automations/webhook integrations. Existing resources are unchanged.
• For product and growth: PMs can now test access-based offers, use first-delivery mail series where automations exist, add delivery-mail personalization through listeners, and monitor requests through a webhook. The package is best positioned as Laravel-native delivery infrastructure, not a replacement for CRM, identity, or full marketing automation.