Weave Code
Mailchimp Laravel Package
statamic-rad-pack/mailchimp
Statamic Mailchimp addon by Rad Pack that connects Statamic forms to Mailchimp audiences, making it easy to capture newsletter signups, map form fields, and manage subscribers without custom integration code.
Subscribe registrations or contact forms to Mailchimp
Frequently asked questions about Mailchimp
- How do I install the Statamic Mailchimp addon?
- Install it with composer require statamic-rad-pack/mailchimp, publish the addon configuration, and set your Mailchimp API key, audience ID, and server prefix in the environment file. Then connect the addon to a Statamic form and map the fields you want to send. The overview describes this as configuration rather than custom integration code.
- Which Statamic and Laravel versions are supported?
- The package is a Statamic addon, so its compatibility follows Statamic majors, which in turn track Laravel and PHP versions. The evaluation context describes a Statamic v4/v5-era fit on modern Laravel and PHP 8.x, but you should confirm the exact composer constraints before installing. Pin a specific version such as ~6.2.0 rather than floating it.
- Can I use this package in a plain Laravel app without Statamic?
- No. This addon registers through Statamic's addon and service-provider lifecycle and hooks Statamic form submissions into Mailchimp subscribe calls, so it is the wrong abstraction for a plain Laravel application. For non-Statamic Laravel apps, a thin Mailchimp HTTP client or SDK wrapper is simpler.
- How do I map form fields to Mailchimp merge fields and tags?
- The addon is designed to map Statamic form fields to a subscriber's email address, Mailchimp merge fields, and tags, with audience settings configured separately. You configure credentials and audience details, then define the field mapping for each form. Validate merge-field names in Mailchimp before relying on them in production.
- Does Statamic Mailchimp support double opt-in and consent capture?
- The provided overview does not document double opt-in or explicit consent capture behavior. Mailchimp audiences often control opt-in settings on the Mailchimp side, but you should verify how the form handler behaves before relying on it for consent. If consent evidence is a compliance requirement, test the exact flow in staging.
- Are Mailchimp subscribe calls synchronous or can they be queued?
- The context does not state whether subscribe calls run synchronously inside the request or can be dispatched to a queue. Synchronous calls would add Mailchimp latency to user-facing form submissions, so this is worth verifying before launch. If queueing is not built in, consider wrapping the subscribe step in your own job or checking the package's handler.
- What happens on duplicate email, unsubscribed contact, or invalid merge field?
- The available material does not specify whether duplicate emails, unsubscribed contacts, or invalid merge fields produce a silent no-op, an exception, or a form validation error. These cases matter because they affect user feedback and whether failed signups are visible. Test each scenario against a staging audience before going live.
- How can I test this addon without hitting a live Mailchimp audience?
- The context does not confirm a built-in testing seam, but you should look for an injectable client or HTTP fake support so CI can run without a live Mailchimp audience. If the addon uses Laravel's HTTP client, Http::fake can isolate subscribe calls in tests. Otherwise, stub the service binding or test against a dedicated sandbox audience.
- Is Statamic Mailchimp maintained and safe for production?
- Treat it as a small, MIT-licensed community addon with limited stars and one or two maintainers, not a vendor-supported product with an SLA. The main production risk is supply chain and upgrade coupling: a Statamic major release can strand the package mid-project. Pin the version, review the source, and have a fork-or-replace plan if maintenance stops.
- What is the 500-record audience pull limit in version 6.2.5?
- Version 6.2.5 reportedly caps audience pulls at 500 records, and a successful response can look identical whether or not more records exist. That matters only if you need to pull audiences out of Mailchimp; the package's main description is about pushing form submissions into Mailchimp. Confirm whether audience pulling is a real requirement before treating the cap as a blocker.
Weaver
How can I help you explore Laravel packages today?