Audience organization
Manage audience lists and segments.
Build email campaigns around your audience
Build email campaigns with audience segments, subject tests, automations, and engagement reports.
Each domain keeps its own audience: subscribers with tags, custom fields, source and consent time, lists, segments by tag, list, field, sign-up date or activity, CSV import with mapping and dedupe, and a suppression list that imports never undo. People sign up on a brand-styled campaign.<domain>/subscribe page, an embedded form or POST /api/v1/subscribe, with double opt-in. Campaigns are built from blocks (heading, text, image, button, divider, two columns, a Coupons offer, footer) on 22 templates, Diwali, Holi, Eid, Christmas, New Year and Independence Day among them, rendered as email-safe HTML with a plain-text part, previewed for desktop and phone, test-sent, scheduled and A/B-tested on the subject line. A cron sends in batches with one-click List-Unsubscribe, a footer with the postal address and a web version at /v/<id>; /u/<token> holds unsubscribe and list preferences. Automations run welcome series and drips (wait, send, add or remove a tag, a condition on opens and clicks). Open and click tracking, reports per campaign and per link, an optional pull from Contacts, and Claude writing a campaign from a brief, subject lines and a send time. Campaign and automation sending ships switched off until the owner turns it on. campaigns.appneural.com holds every domain; campaign.<domain> holds one domain's audience and campaigns.
What Campaigns does for you.
Manage audience lists and segments.
Build campaigns from blocks with A/B subject choices.
Use automations with open and click reports.
A suggested path for Campaigns. What you can do depends on your access in the app.
Start with the relevant list or segment.
Prepare email blocks and subject variants.
Use open and click reports to assess the campaign.
Live host, inventory, governance, health checks, verification, dependencies and history.
Each domain keeps its own audience: subscribers with tags, custom fields, source and consent time, lists, segments by tag, list, field, sign-up date or activity, CSV import with mapping and dedupe, and a suppression list that imports never undo. People sign up on a brand-styled campaign.<domain>/subscribe page, an embedded form or POST /api/v1/subscribe, with double opt-in. Campaigns are built from blocks (heading, text, image, button, divider, two columns, a Coupons offer, footer) on 22 templates, Diwali, Holi, Eid, Christmas, New Year and Independence Day among them, rendered as email-safe HTML with a plain-text part, previewed for desktop and phone, test-sent, scheduled and A/B-tested on the subject line. A cron sends in batches with one-click List-Unsubscribe, a footer with the postal address and a web version at /v/<id>; /u/<token> holds unsubscribe and list preferences. Automations run welcome series and drips (wait, send, add or remove a tag, a condition on opens and clicks). Open and click tracking, reports per campaign and per link, an optional pull from Contacts, and Claude writing a campaign from a brief, subject lines and a send time. Campaign and automation sending ships switched off until the owner turns it on. campaigns.appneural.com holds every domain; campaign.<domain> holds one domain's audience and campaigns.
The simple update list at subscribe.<domain> belongs to Subscriptions; the people themselves belong to Contacts and Customers; coupon codes belong to Coupons.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
campaigns.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.