Installation

Require the package with Composer. The service provider and the Campaigns facade alias are auto-discovered — no manual registration:

composer require roundly-consulting/campaigns-for-laravel

Companion packages

Composer also installs the packages Campaigns builds on — contacts-for-laravel, options-for-laravel and enums-for-laravel, plus package-toolkit-for-laravel. Their migrations are publish-only. The send defaults (sender, sending queue, channel) are read through options-for-laravel whenever a campaign is prepared and whenever a recipient job is built, so publish and run its migration. The contacts migration is what lets you address campaigns from contact records:

php artisan vendor:publish --tag="options-migrations"
php artisan vendor:publish --tag="contacts-migrations"
php artisan migrate

Config file

The config file is optional — every key has a default, and all but one are env-backed. Publish it only to override:

php artisan vendor:publish --tag="campaigns-config"

Campaign tables (optional)

The default in-memory store needs no tables of its own. Only the database store needs the campaigns and campaign_recipients tables. The migrations are never loaded automatically — publish them first, or a bare migrate won’t create them:

php artisan vendor:publish --tag="campaigns-migrations"
php artisan migrate

Job batches

Every campaign runs as a Laravel job batch, stored in the job_batches table. New Laravel 12 and 13 apps create it in the default jobs migration; if yours doesn’t have it, generate it:

php artisan make:queue-batches-table
php artisan migrate

Publish tags

• campaigns-config — config/campaigns.php.
• campaigns-migrations — create_campaigns_table and create_campaign_recipients_table, timestamped on publish in that order.