Managing Live Campaigns

This tab allows you to verify that the Slate integration is working correctly before relying on it for live sends. You can enter up to 5 test recipient records, each with a first name, last name, and email address.

When submitted, the system generates a test CSV with the appropriate Slate field mappings and drops it to the configured Slate connection. A success screen confirms delivery. This lets you confirm that the integration pipeline (field mappings → CSV generation → SFTP delivery) is functioning end-to-end before real student data is processed.

The Reschedule Delivery action allows you to adjust the delivery date and/or time of any future (unsent) emails in the campaign. Emails already sent are shown as read-only with a "Sent" badge. 

• Shift Subsequent Dates toggle — When enabled (default), changing the date of one email automatically shifts all subsequent emails by the same number of days, maintaining the relative spacing of the entire schedule. When disabled, only the individual email you edit is moved. 

• Time editing — Each future email also has a time picker, allowing you to change the send hour independently.

• Validation — The system enforces that all rescheduled emails must be at least 3 days from the current date and at least 2 days apart from each other. The Save button is disabled until the reschedules email meets the requirements.

Displays a table of all lead profiles currently opted out of the campaign. For each profile, it shows their name, email address, the source of the opt-out (Manual, CSV Upload, API, or Web Service), the date/time it occurred, and the user who performed it (or "via API" if automated). An optional reason can be viewed via a tooltip.

You can remove an opt-out for any individual by clicking the trash icon next to their row, which reinstates them into the campaign audience.

This tab allows you to manually search the campaign's audience and select specific lead profiles to opt out. You can:

• Search by name or email using the search bar (with a 500ms debounce).
• Select one or more profiles using checkboxes.
• Optionally provide a reason for the opt-out (e.g., "requested removal," "legal requirement").

Submitting the selection opts out the chosen profiles and cancels any of their pending emails. The success message confirms how many pending emails were cancelled.

This tab enables bulk opt-outs via file upload. You upload a CSV or TXT file containing one email address per line. The file can be selected via file browser or drag-and-dropped onto the upload zone. You can also provide an optional reason for the bulk suppression.

Upon processing, a results summary shows: how many profiles were suppressed, how many pending emails were prevented from sending, and how many email addresses were not found in the campaign audience.

This tab configures an automated, recurring suppression sync via an external web service endpoint. You provide:

• Endpoint URL — A URL that returns a CSV of email addresses to suppress (e.g., a Slate query endpoint).
• Username and Password — Credentials for authenticated access to the endpoint.

Once saved, Halda will periodically fetch data from the endpoint and automatically apply suppressions. The tab also shows the last synced timestamp if a sync has previously occurred. If a configuration already exists, you can update the URL/username and leave the password blank to keep the existing credentials unchanged.