Statamic Marketing Laravel Package

Product Decisions This Supports

• Control Panel information architecture: The addon participates in a shared settings navigation model (settingsNavParent() returning [section, name]), letting it nest its settings as a sub-item ("Einstellungen") under its own CP navigation entry rather than occupying a standalone settings slot. This is directly relevant to decisions about how much CP surface area an addon should own.
• Addon-suite consolidation: When paired with statamic-brand-context ≥ 1.16, addons without their own navigation collapse into a single "Addon-Suite" page under Settings. This supports a roadmap decision to present a coherent suite rather than a scattering of per-addon settings pages — useful if you ship or maintain multiple addons.
• Upgrade sequencing / dependency gating: The navigation behavior is version-conditional — older brand-context versions silently ignore the new method and keep the previous layout. That makes it a coordination decision (upgrade brand-context alongside the addon) rather than a feature-flag decision.
• Measurement fidelity for login/link tracking: v2.39.2 makes click tracking recognise percent-encoded login link paths. This is a data-quality decision, not a feature decision: if we generate login or magic links whose paths carry percent-encoded segments (or pass them through redirectors, URL shorteners, or email clients that re-encode), clicks on those links were previously not counted. Decide whether reporting that depends on this addon's click counts is trustworthy for the traffic we actually send.
• Build vs. buy: Low-stakes on both axes. The nav change argues for staying on the package's release track rather than forking CP navigation behavior; the click-tracking fix argues the same for URL parsing — percent-encoding edge cases are exactly the kind of thing you do not want to reimplement and maintain in-house.
• Low-risk maintenance cadence: Patch-level release, no migration, no new config key. It can ride along with a routine dependency bump without a dedicated release window or support/comms plan.
• Version drift to close out: We are assessing from v2.30.0 to v2.39.2 — nine minor releases and many patches of accumulated change summarised only by terse release notes. That gap itself is a decision input: schedule a deliberate bump-and-verify rather than continuing to reason from a stale baseline.

When to Consider This Package

• Adopt when: you run Statamic with a Control Panel that already has (or will have) multiple settings-bearing addons, and you want them grouped predictably instead of each claiming its own Settings entry. The value compounds if you also use statamic-brand-context ≥ 1.16, since only then does the nested/"Addon-Suite" grouping actually take effect.
• Adopt when: click tracking of login or magic links feeds a metric someone acts on — onboarding completion, activation, campaign attribution. v2.39.2 closes a specific under-counting gap (percent-encoded paths), so re-baseline any dashboard built on this data after upgrading rather than comparing pre- and post-upgrade numbers directly.
• Adopt when: you want an addon that tracks platform navigation conventions and ships non-breaking, migration-free upgrades — a reasonable signal of maintenance health for a small utility dependency.
• Look elsewhere / defer when: you are pinned to an older statamic-brand-context (< 1.16). The navigation declaration is inert there, so upgrading buys you nothing on that front until brand-context moves; schedule them together. (The click-tracking fix is independent of that gate and lands regardless.)
• Look elsewhere when: your CP is intentionally flat and single-addon, so the grouping machinery adds conceptual overhead with no user-visible benefit — and you do not depend on the tracking behaviour.
• Caveat on scope: the release notes remain title-level. For v2.39.2 we know what was fixed but not whether historical clicks were dropped from storage (unrecoverable) versus merely mis-attributed in reporting, and we have no statement on test coverage for the tracking path. Treat the tracking-accuracy claim as directionally correct until verified against our own link formats. Likewise, this assessment covers navigation integration and one tracking fix — not the addon's core functionality, performance, or security posture in full.

How to Pitch It (Stakeholders)

For executives: Two small, low-risk changes on the normal release track, nothing to migrate, no new configuration, no downtime. The first is cosmetic-but-useful: our addon's settings slot neatly under a single navigation entry, and on the newer brand-context version settings from multiple addons consolidate onto one "Addon-Suite" page instead of cluttering the admin menu — a tidiness and discoverability win for editors. The second is a correctness fix: click tracking now counts login links whose paths are percent-encoded, which were previously slipping through. That means the numbers we report on link engagement get more complete, not that any new capability appears. The one caveat worth flagging is that we are several releases behind, so this is a good moment for a routine bump rather than a targeted patch.

For engineering: The addon implements settingsNavParent(), declaring the [section, name] of its own CP nav entry so its settings render as a sub-item beneath it — gated on statamic-brand-context ≥ 1.16, with earlier versions ignoring the method and retaining current layout, so there is no regression risk if we ship out of order. v2.39.2 additionally fixes click tracking to recognise percent-encoded login link paths. Upgrade path is clean: no migration, no config key, patch-level. Recommended action: bump to the current release on the normal cadence, align brand-context to ≥ 1.16 if we want the grouped nav to actually appear, and run two checks — a CP smoke test on nav placement (the visual outcome differs by brand-context version) and an end-to-end click test using a login link with an encoded path to confirm the click registers. Note the 2.30.0 → 2.39.2 gap; skim CHANGELOG.md for anything not surfaced in the release notes before we commit to the bump.