Halda Email Campaign Suppression

Overview

Halda can automatically suppress students from email campaigns based on institution-defined criteria (e.g., application completed, event registered, deposited, enrolled, etc.).

This integration uses a Slate Web Services query (CSV output) that returns students who should be excluded from a specific Halda email campaign.

The query is delivered via the Halda suitcase and may be:

• Used as-is
• Updated with campaign-specific filters
• Duplicated for each unique campaign

Important: One Suppression Query Per Campaign

Each Halda campaign must have its own suppression list.

If you are running multiple campaigns (e.g., Fall App Campaign, Deposit Campaign, Event Reminder Campaign), you must:

• Duplicate the suppression query
• Configure unique filter logic per campaign
• Generate a separate Web Service endpoint for each

This ensures suppression rules remain campaign-specific and do not conflict.

What the Query Returns

The suppression query exports:

• Person First
• Person Last
• Person Email

Email address is the key field used for suppression.

Do not modify export field names.

Required Setup Steps

Step 1: Locate the Suitcased Query

1. Navigate to Queries / Reports
2. Open the Halda Email Campaign Suppression Query
3. Confirm:
   • Base: Configurable Joins – Person
   • Execution Mode: Retrieve all records each time query is run
   • Exports:
     
     
     • Person First
     • Person Last
     • Person Email
       
       

Step 2: Configure Campaign Suppression Criteria (Required)

Under Filters, update:

*** UPDATE – CAMPAIGN SUPPRESSION CRITERIA ***

Replace this placeholder with your campaign-specific suppression logic.

Examples:

• Application Status = Complete
• Event Registration Status = Registered
• Deposit Status = Deposited
• Student Stage = Enrolled

The filter should identify students who should no longer receive that campaign’s emails.

Step 3: Duplicate for Additional Campaigns (If Needed)

For each new campaign:

1. Click Copy on the suppression query
2. Rename clearly (e.g., Halda Suppression – Fall App Campaign)
3. Update the filter logic
4. Configure Web Services (see below)

Each campaign must have its own Web Service endpoint.

Step 4: Enable Web Services (CSV Output)

1. Open the query
2. Click Edit Web Service
3. Set:
   • Service Type: CSV
   • Include NULLs: Include NULL Values
4. Click Save

Slate will generate the CSV Web Service endpoint URL.

No custom parameters are required for suppression queries.

Step 5: Configure Grantee 

Halda authenticates using Basic Authentication via a Web Service Grantee.

1. Open the Web Service configuration
2. Click Edit Permissions
3. Click Add Grantee
4. Configure:
   
   
   • Type: Username
   • Username: (create credential for Halda)
   • Password: (create secure password)
   • Permissions: Web Service
5. Save

Halda will call the CSV Web Service endpoint using these credentials.

You may reuse the same credential as the Email Metrics Web Service or create a separate one.

What to Provide to Halda (Securely)

For each campaign, please securely provide:

• The CSV Web Service endpoint URL
• The Web Service Grantee username
• The Web Service Grantee password
• The associated Halda campaign name

Credentials should be transmitted securely.

Ongoing Behavior

Halda will:

1. Authenticate to the CSV Web Service
2. Retrieve all students matching suppression criteria
3. Suppress those students from the associated campaign
4. Repeat regularly to ensure newly qualifying students are excluded

No scheduled exports or manual uploads are required.

Alternative Suppression Options

In addition to Web Service integration, suppression can also be managed:

• Manually within the Halda application
• Via CSV file upload to Halda

Institutions may choose the method that best fits their operational workflow.

Web Service integration is recommended for automated, ongoing suppression.

Best Practices

• Keep suppression criteria tightly aligned to campaign goals
• Test query results before enabling Web Service
• Maintain separate queries per campaign
• Coordinate with Halda before changing export structure