Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Statamic Marketing

Statamic Marketing Laravel Package

goldnead/statamic-marketing

A marketing addon for Statamic that puts essential tools in your control panel: cookie consent, tracking and analytics scripts, and campaign settings, configurable without editing templates. Keeps marketing setup simple and centralized at the CMS level.

View on GitHub
Deep Wiki
Context7

goldnead/statamic-marketing is a Statamic addon that brings essential marketing tooling into your Laravel-powered site. It lets you manage tracking scripts, consent, and campaign-related settings from the control panel—no template hacking required—keeping your marketing stack clean and configurable.

  • Control-panel management of marketing scripts and settings
  • Configurable cookie/consent handling
  • Add marketing assets without editing templates
  • Statamic-native configuration via simple config files
  • Lightweight and cache-safe integration
Frequently asked questions about Statamic Marketing
What does the Goldnead Statamic Marketing addon do?
Goldnead's Statamic Marketing addon brings marketing tools into the Statamic control panel so you can manage promotional content and campaign settings alongside your entries. It is designed to fit Statamic's familiar workflow and keep marketing tasks close to your content. The addon integrates with the Control Panel settings navigation rather than replacing core content features.
How do I install goldnead/statamic-marketing?
Installation is standard Composer-based addon installation for a Statamic project. Run composer require goldnead/statamic-marketing and follow normal Statamic addon registration steps for your project. The v2.30.0 release notes state that no database migrations or new config keys are required, so the upgrade itself is a Composer dependency update.
Which Laravel, PHP, and Statamic versions are supported?
The provided assessment does not list the addon's broader PHP, Laravel, or Statamic version constraints. Before upgrading in production, check the package's composer.json and Packagist metadata for the supported ranges. Test the addon against your project's exact Statamic and Laravel versions in staging.
Is statamic-brand-context a hard or optional dependency?
The assessment describes statamic-brand-context as an optional integration rather than a hard requirement. If statamic-brand-context 1.16 or newer is present, the addon can use the new settingsNavParent() hook to declare a parent navigation entry. If it is absent or older, the addon falls back to its previous control panel layout rather than failing.
Does updating to v2.30.0 require database migrations or config changes?
No. The v2.30.0 release explicitly states that there is no migration and no new config key. Upgrading is a Composer dependency update, and no data migration window is needed. This keeps operational overhead low for existing installations.
What is the settingsNavParent() hook and how does it affect the control panel?
settingsNavParent() is a standard-style extension point used to declare a parent navigation entry in the Statamic Control Panel settings area. It is low-coupling and only affects the CP settings layout when statamic-brand-context 1.16 or newer is installed. Older brand-context versions ignore the method, preserving the previous navigation behavior.
Will older statamic-brand-context versions break the addon?
No, older brand-context versions should not break the addon. The change is additive and backward compatible: if brand-context is absent or older than 1.16, the navigation falls back to the previous layout instead of failing. Version skew may change where settings appear in the control panel, but it should not affect core addon functionality.
Are there automated tests for control panel navigation?
The provided assessment does not confirm whether automated tests cover control panel navigation. It is based solely on the v2.30.0 release notes and does not include test suite details. Review the repository's test coverage and run a brief QA of the CP settings menu in staging.
Can this addon conflict with other Statamic addons that declare the same settings parent?
Potential conflicts are possible if multiple addons declare the same parent navigation entry or rely on the shared Addon-Suite page. The technical risk is described as low, and the primary concern is CP navigation presentation rather than core functionality. Validate the settings menu in staging when installing multiple addons that extend CP navigation.
What is the maintenance and support policy for older brand-context versions?
A formal support policy for older statamic-brand-context versions is not documented in the provided context. Maintenance burden is described as low because there are no new config keys or migrations, and standard Composer dependency management applies. Document any control panel navigation changes for administrators and verify behavior in staging before production upgrades.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
uni-method/symfony-lib
tacticmedia/scim-server-bundle
neika-ai/symfony-bundle
mattleads/agent-publishing-bundle
glavweb/framework-bundle
glavweb/extra-bundle
glavweb/api-bundle
glavweb/admin-bundle
adachsoft/api-version-bundle
elsayed85/laravel-api-exceptions
ouhssini/laravel-demo-mode
daworks/ncloud-outbound-mailer-driver
gp247/cms
ignibyte/aic-gates
nexa-merchant/blog
novasa/laravel-language-center
opencage/geocode
adolfoholzer/parameters
livenetworks/ln-starter
cgv/localized-resource