Skip to app details
Back to app library
APPNEURAL APP FAMILYMarketing & Branding

Campaigns

Build email campaigns around your audience

Build email campaigns with audience segments, subject tests, automations, and engagement reports.

01 / OVERVIEW

See where it fits in your day.

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.

A LOOK INSIDEExample layout · sample content
An email campaign taking shape
T
AudienceWelcome email
Product update
Event invitation
02 / CAPABILITIES

Built around the work you do.

What Campaigns does for you.

01

Audience organization

Manage audience lists and segments.

02

Email building

Build campaigns from blocks with A/B subject choices.

03

Campaign reporting

Use automations with open and click reports.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Campaigns. What you can do depends on your access in the app.

01

Choose the audience

Start with the relevant list or segment.

02

Build the campaign

Prepare email blocks and subject variants.

03

Review the reports

Use open and click reports to assess the campaign.

YOUR NEXT MOVE

Make Campaigns part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE— items
P2PARTIALLY VERIFIEDPUBLISHED
Overview

Purpose and boundaries

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.

Email marketing for a connected domain: an audience with lists, segments and a suppression list, sign-up forms, campaigns built from blocks with A/B subject tests, automations, and open and click reports.

The simple update list at subscribe.<domain> belongs to Subscriptions; the people themselves belong to Contacts and Customers; coupon codes belong to Coupons.

Priority
P2
Portfolio
Marketing & Branding
Capability
Marketing & Branding
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-16T04:18:11.984Z
Semantic inventory

Every number says what it counts

—Count unavailabletrackedEntityCount · catalog-api:unavailable
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

campaign schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

campaigns.appneural.com DEPLOYED

campaigns.appneural.com

Worker
campaign-catalog
Health
HEALTHY
Last deployment
2026-11-08 10:24:36
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

Repository provider is not connected. Existing references remain unverified.

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is partially verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app