Home/Knowledge Base & Documentation/v2.6 Live
Complete Step-by-Step Product Guide

Master Email Marketing with SendSurface

From connecting your SMTP provider to launching your first campaign, learn everything you need to use SendSurface with confidence.

Categories:
53 min total read time
12 modules covering the entire platform
BYOS Model: Zero markup on email sends
1Foundation & Architecture

Step 1 — Getting Started with SendSurface

SendSurface is an email marketing platform built around the Bring Your Own SMTP (BYOS) model. Instead of acting as an email relay or forcing marked-up sending tiers, SendSurface provides campaign creation, contact management, and reporting while connecting directly to your chosen SMTP provider.

The SendSurface BYOS Model

What SendSurface Provides:

Visual & HTML email editor, subscriber and list management, unsubscribe and global suppression protection, open/click tracking, inbound/outbound webhooks, and campaign reporting.

What Your SMTP Provider Provides:

Email transmission infrastructure, IP reputation, sending quotas, and direct per-email billing (e.g. Amazon SES, SendGrid, Mailgun, Brevo, SMTP2GO, SMTP.com, or Zoho ZeptoMail).

The SendSurface 6-Step Workflow

Step 1
Create Account
Register workspace
Step 2
Connect SMTP
Add provider relay
Step 3
Verify Domain
Configure SPF/DKIM
Step 4
Import Contacts
Upload CSV audience
Step 5
Design Campaign
Visual & HTML editor
Step 6
Send & Monitor
Track live activity data

Understanding Workspaces & Account Approval

SendSurface enforces complete tenant and workspace isolation. Each workspace maintains its own isolated contact lists, global suppression blacklist, SMTP connections, custom tracking domains, and webhooks. When creating a new account, accounts are activated immediately or placed in brief verification review to preserve IP reputation and platform compliance.

2Connect Your Email Provider

Step 2 — Connect Your SMTP Provider

SendSurface connects directly to your external email delivery provider over encrypted SMTP. Passwords and secrets are encrypted server-side using AES-256.

Supported SMTP Presets & Default Settings

ProviderDefault HostPortEncryptionUsername Format
SMTP.comsend.smtp.com2525 / 587STARTTLSSMTP.com Sender Username
Zoho ZeptoMailsmtp.zeptomail.com587 / 465STARTTLS / SSLemailapikey
Brevosmtp-relay.brevo.com587 / 465 / 2525STARTTLS / SSLBrevo SMTP Login (use SMTP Key)
Amazon SESemail-smtp.us-east-1.amazonaws.com587STARTTLSSES SMTP Access Key ID
SendGridsmtp.sendgrid.net587STARTTLSapikey
Mailgunsmtp.mailgun.org587STARTTLSpostmaster@yourdomain.com
SMTP2GOmail.smtp2go.com587STARTTLSSMTP2GO Username
Mailjetin-v3.mailjet.com587STARTTLSMailjet API Key
Elastic Emailsmtp.elasticemail.com2525 / 587STARTTLSElastic Email Account Email
Custom VPS / SMTPmail.yourdomain.com587 / 465TLS / SSLSMTP Username

How to Add and Test an SMTP Connection

  1. Open Sending Connections: Navigate to the Sending Connections tab in your customer console.
  2. Click “Add Connection”: Choose your provider from the dropdown. SendSurface automatically pre-fills standard hostnames, ports, and encryption protocols.
  3. Enter Credentials: Provide the SMTP username and password supplied by your provider. (For SendGrid, always enter apikey as the username).
  4. Test Connection: Click Test Connection. SendSurface opens a live socket to your mail host, verifies the TLS handshake, and validates SMTP authentication.
  5. Save and Set Default: Click Save Connection. Check Set as Default Connection if this is your primary sending relay.
Important: Port 25 vs Port 587

Most cloud environments and VPS hosts block outbound traffic on port 25 to mitigate spam. Always use Port 587 (STARTTLS) or Port 465 (SSL) for reliable connectivity.

3Domain Authentication

Step 3 — Verify Your Sending Domain

To ensure maximum inbox placement and avoid the spam folder, major mailbox providers (Google, Yahoo, Microsoft) require cryptographic proof that you own your sending domain.

SPF
Sender Policy Framework

A DNS TXT record declaring which mail servers are authorized to send email using your domain.

v=spf1 include:amazonses.com ~all
DKIM
DomainKeys Identified Mail

A public-key cryptographic signature attached to email headers proving messages were not forged.

k=rsa; p=MIGfMA0GCSqGSI...
DMARC
Domain Message Auth

Policy record instructing receiving servers how to handle emails failing SPF or DKIM checks.

v=DMARC1; p=quarantine; rua=...

How Domain Verification Works in SendSurface

  1. Add Domain in SendSurface: Go to the Sending Domains tab in your console, enter your root domain (e.g. company.com), and click Add Domain.
  2. Retrieve DNS Records from Your SMTP Provider: In your SMTP provider's dashboard (Amazon SES, SendGrid, Mailgun), generate the specific SPF, DKIM, and DMARC TXT/CNAME records.
  3. Publish in Your DNS Registrar: Log into Cloudflare, GoDaddy, Namecheap, or Route 53 and publish the records.
  4. Wait for Propagation: DNS propagation typically takes between 5 minutes and 24 hours depending on TTL settings.
4Branded Link Tracking

Step 4 — Configure a Custom Tracking Domain

When you send an email with open or click tracking enabled, links are rewritten to record activity data before redirecting the recipient to their destination. Using a branded tracking subdomain (e.g. track.yourdomain.com) ensures links match your sender identity and avoids spam filtering flags caused by mismatched domains.

Required DNS A Record for Custom Tracking

TypeHost / SubdomainValue / Tracking Server IPTLS Provisioning
Atrack37.27.22.133Automatic (Caddy On-Demand TLS 1.3)

Replace track with your chosen subdomain prefix (e.g., links, click, or email).

Automated SSL Certificates

SendSurface runs Caddy servers on the tracking server IP. As soon as your DNS A record points to 37.27.22.133, Let's Encrypt / ZeroSSL TLS certificates are provisioned on-demand automatically with zero manual certificate management.

Live Tracking Diagnostics

Click Run Diagnostics in your tracking dashboard anytime. SendSurface tests 5 phases: authoritative DNS resolution, TCP port 80/443 handshake, valid TLS certificate validation, transparent pixel rendering, and signed redirect execution.

Verified Tracking Domain Requirement

To protect sender reputation and link trust, SendSurface requires your workspace's custom tracking domain to pass DNS and HTTPS verification before launching campaigns.

5Subscriber & List Management

Step 5 — Contacts and Audience Lists

SendSurface provides scalable contact management with support for custom properties, segmentation filters, automated conflict resolution, and workspace-wide global suppression protection.

Practical CSV Import Walkthrough

  1. Prepare Your CSV File: Format your file with column headers on the first line. Save as UTF-8 encoded CSV.
  2. Select Audience List: Go to Contacts, select or create your destination list, and click Import CSV.
  3. Upload File: Drag and drop your .csv file or click to browse.
  4. Map Columns: Map your CSV headers to SendSurface core fields: email (required), firstName, lastName, tags, plus any custom fields you include (such as plan, city, or company).
  5. Duplicate Resolution: SendSurface automatically resolves duplicate emails against ON CONFLICT (workspace_id, email), updating existing contacts without creating duplicate database rows.
Example Valid CSV Structure:
email,firstName,lastName,plan,city
jane@example.com,Jane,Doe,Enterprise,Austin
alex@sample.org,Alex,Smith,Pro,London
maria@techfirm.io,Maria,Garcia,Starter,Berlin

Global Suppressions & Unsubscribes

SendSurface maintains an authoritative Global Suppressions blacklist per workspace. When an address is suppressed (via hard bounce, spam complaint, or manual blacklist), it can never be mailed by any campaign, even if imported into multiple lists. Resubscribing a contact is only permitted if the email is not present on the blacklist.

6Content & Template Design

Step 6 — Design Your First Email

SendSurface includes a flexible email editor supporting visual rich-text composition and raw HTML source mode with live desktop and mobile previews.

Visual Rich-Text & Templates

Edit headings, body text, images, links, call-to-action buttons, and personalization tags directly in the visual canvas or start from saved templates.

Raw HTML Source Mode

Switch directly between visual editing and raw HTML source code to paste custom email templates or fine-tune layout markup.

Dynamic Personalization Merge Tags

Merge VariableReplacement ValueExample Output
{{first_name}}Recipient's first name (falls back to “there”)“Hello Jane,”
{{last_name}}Recipient's last name“Doe”
{{email}}Recipient's email address“jane@example.com”
{{custom_field_key}}Any custom attribute stored on the contact“Enterprise”
{{unsubscribe_url}}Signed 1-click unsubscribe endpoint (RFC 8058)https://track.domain.com/track/unsub/...

Testing Before Launch

Always use the Send Test Email button inside the builder. Provide your personal address to inspect responsive rendering across Gmail, Apple Mail, and Outlook before queueing messages to your subscribers.

7Campaign Sending

Step 7 — Create and Send Your First Campaign

Launching a campaign in SendSurface is guided by an intuitive 13-point wizard that ensures technical compliance, audience accuracy, and deliverability protection.

The Complete Campaign Creation Workflow

1. Campaign NameInternal label for your dashboard and reports.
2. Select SMTP ConnectionChoose your verified sending relay (e.g. SES or SendGrid).
3. Choose Tracking DomainSelect verified branded workspace domain (e.g., track.yourdomain.com).
4. From Name & EmailName and email your recipients see in their inbox.
5. Reply-To AddressMailbox where direct recipient replies are routed.
6. Subject Line & PreheaderPrimary subject line plus inbox snippet preview text.
7. Target AudiencesSelect one or more contact lists and dynamic segments.
8. Real-Time Audience CountCalculates active subscribers minus suppressed contacts.
9. Template / Email DesignBuild visually, write HTML, or select saved template.
10. Desktop & Mobile PreviewVerify rendering across desktop and mobile simulator.
11. Send Test EmailSend a test proof copy to your personal inbox.
12. Review Quality ChecklistAudit links, unsubscribes, and SMTP credentials.
13. Send CampaignReview your pre-flight summary and send immediately via your SMTP connection.

Essential Pre-Send Quality Checklist

SMTP connection tested and operational
From domain has active SPF & DKIM records
Unsubscribe link {{unsubscribe_url}} included
All links tested and redirecting correctly
Suppressed and bounced contacts excluded
Test email reviewed on desktop and mobile
8Live Analytics & Reporting

Step 8 — Track Campaign Performance and Analytics

SendSurface provides real-time campaign performance analytics with detailed distinction between socket acceptance and verified mailbox delivery.

Critical Industry Concept: Sent vs. Delivered
Sent:

Your SMTP provider accepted the email over the network socket (250 OK: Message queued for delivery). The message has left SendSurface, but may still encounter downstream server deferrals or bounces.

Delivered:

The recipient's mailbox server (e.g. Gmail or Yahoo) confirmed delivery of the message without rejection. This status is updated automatically when you configure inbound provider webhooks.

SendSurface Campaign Metrics

Unique Opens
1x1 Pixel

Recorded when email client renders image. (Note: Apple MPP proxies affect open counts).

Unique Clicks
HMAC Redirect

Cryptographically signed URL redirecting through your tracking domain.

Hard Bounces
Permanent (550)

Mailbox does not exist. Automatically suppressed across workspace.

Unsubscribes
1-Click / Footer

RFC 8058 header clicks or footer link clicks. Immediately marked UNSUBSCRIBED.

Granular Recipient Activity Log

Click View Report on any campaign in your console to access the individual recipient audit trail. Filter by DELIVERED, OPENED, CLICKED, or BOUNCED, inspect timestamps, and identify delivery issues.

9Two-Way Webhook Connections

Step 9 — Webhooks: Connect Email Providers and External Applications

SendSurface features a two-way webhook system: Inbound Provider Webhooks capture delivery and bounce events from email services, while Outbound Webhooks stream campaign events to your external backend, CRM, or database.

Two-Way Webhook Flow
1. Inbound Events:[Email Provider] → (POST Webhook) → [SendSurface Webhook Receiver]
2. Outbound Streaming:[SendSurface Webhooks] → (HTTP POST) → [Your CRM / Slack / Backend]

A.Email Providers → SendSurface (Inbound Webhooks)

By default, campaigns are marked SENT upon SMTP acceptance. Inbound webhooks allow your provider to push live delivery confirmations, bounces, and complaints back to SendSurface.

Supported Inbound Providers & Authentication Formats:
1. Amazon SES (Amazon EventBridge & AWS SNS):

Connect Amazon SES using either Amazon EventBridge API Destinations (recommended for Delivery, Bounce, Open, Click, DeliveryDelay, Rendering Failure, and Subscription events) or an Amazon SNS topic subscription targeting /api/webhooks/incoming/amazon-ses/{workspace_id}.

2. Brevo (Sendinblue):

In Brevo Dashboard → Settings → Webhooks, enter /api/webhooks/incoming/brevo/:workspaceId. Under Authentication method, select Token and enter your verification secret. SendSurface accepts both Token: <token> and Authorization: Bearer <token>.

3. SendGrid:

In SendGrid Settings → Mail Settings → Event Webhook, paste your SendSurface endpoint and verification key. Supports Delivered, Dropped, Bounced, and Spam Report events.

4. Mailgun:

Configured via Mailgun Webhooks. Validates incoming requests using cryptographic HMAC-SHA256 signatures generated from your Mailgun HTTP Webhook Signing Key.

5. Postmark & Mailjet:

Enter your endpoint in Server → Webhooks (Postmark) or Rest API Event API (Mailjet). Tracks delivery receipts and hard bounce suppression updates.

B.SendSurface → External Applications (Outbound Webhooks)

Stream real-time campaign events to your own servers, CRM, analytics pipeline, or Zapier/Make webhook endpoints.

Example Outbound Webhook JSON Payload:
{
  "event": "recipient.delivered",
  "workspaceId": "ws_example",
  "campaignId": "camp_892173",
  "recipientEmail": "alex@sample.org",
  "timestamp": "2026-11-06T10:30:00Z",
  "provider": "AMAZON_SES",
  "messageId": "<0100018d-msg-sample@email.amazonses.com>"
}

Common Webhook Troubleshooting Solutions

  • HTTP 401 Unauthorized: Ensure your provider configuration includes the exact secret token generated in SendSurface. (For Brevo, paste into the Token authentication field).
  • HTTP 404 Not Found: Check that your webhook URL contains your valid workspace ID (e.g. /api/webhooks/incoming/brevo/YOUR_WORKSPACE_ID).
  • Campaign stays on SENT: Generic SMTP servers (like bare Postfix or cPanel mail) do not push webhooks. To see DELIVERED status, pair your connection with a supported webhook provider (such as Amazon SES, Brevo, SendGrid, Mailgun, Postmark, Mailjet, SMTP2GO, Mailtrap, MailerSend, or SparkPost).
10Compliance & Best Practices

Step 10 — Account Security, Compliance and Best Practices

Responsible email marketing protects your sender reputation, keeps your IP addresses clean, and supports compliance with email regulations (CAN-SPAM, GDPR, CASL, and RFC standards).

Permission-Based Sending

Only email subscribers who have explicitly opted into receiving messages from your organization. Never purchase, rent, scrape, or append third-party contact lists.

Strict Bounce Thresholds

Keep your hard bounce rate strictly below 2.0% and spam complaints below 0.1% (1 per 1,000 sent). Exceeding these limits risks immediate provider suspension by SES, Mailgun, or SendGrid.

RFC 8058 1-Click Unsubscribe

SendSurface automatically attaches List-Unsubscribe: One-Click headers to every sent campaign, updating opted-out contacts to UNSUBSCRIBED.

Credential Security

Never share API keys or webhook secrets in public repositories. SendSurface encrypts SMTP passwords using AES-256 and enforces HTTPS-only webhook delivery.

* Disclaimer: SendSurface provides software tools for email management. Customers remain solely responsible for ensuring compliance with applicable regional laws, CAN-SPAM, GDPR, and their provider terms of service.
11Interactive Knowledge Base

Step 11 — Troubleshooting and Frequently Asked Questions

Searchable solutions to common questions across email providers & integrations, SMTP relays, domain verification, tracking, audience imports, and webhook delivery.

12Email Providers & Integrations
Inbound Event Webhooks · 8 min read

How to Connect Amazon SES to SendSurface Using EventBridge Webhooks

Connect Amazon Simple Email Service (Amazon SES) to SendSurface through Amazon EventBridge API Destinations so campaign reporting and recipient timelines update automatically in real time.

Important: Inbound Event Webhook Integration Only (Not Mailbox Receiving)

This is an inbound webhook integration for receiving Amazon SES email delivery and engagement event notifications. It is NOT an inbound email receiving or mailbox integration for reading replies.

Article Contents

Overview

SendSurface integrates with Amazon SES through Amazon EventBridge API Destinations. When Amazon SES emits email delivery and engagement events for messages sent through your AWS account, EventBridge pushes those JSON notifications securely over HTTPS to your SendSurface workspace webhook endpoint.

Supported Amazon SES Event Notifications:
Email DeliveredDelivery
Email Bounced (Hard & Soft)Bounce
Email OpenedOpen
Email ClickedClick
Delivery DelayedDeliveryDelay
Rendering FailureRendering Failure
Subscription EventsSubscription

Step 1: Get Your SendSurface Webhook Details

  1. Log in to your SendSurface account.
  2. In the Console left sidebar, open Webhooks and make sure the Email Providers → SendSurface (Inbound) tab is active.
  3. Click Connect Email Provider and select Amazon SES (or open your existing Amazon SES integration and click Setup Guide).
  4. Copy these two workspace-specific values:
    • Webhook Endpoint URL
    • Webhook Verification Secret / Token
Endpoint URL Path Format (copy your exact workspace URL from SendSurface):
https://<your-sendsurface-domain>/api/webhooks/incoming/amazon-ses/{workspace_id}
Important: Each workspace has its own Webhook Endpoint URL and Verification Secret. Copy the live values directly from your SendSurface Console rather than sharing credentials across workspaces.
Open Webhooks Settings

Step 2: Create an Amazon EventBridge Connection

  1. Open the AWS Management Console and navigate to Amazon EventBridge in the same AWS region as your Amazon SES identity.
  2. In the left menu under Integration, open API destinations, select the Connections tab, and click Create connection.
  3. Enter a Connection name such as sendsurface-ses.
  4. For Destination type, choose Other.
  5. For Authorization type, select API key.
  6. Set the API key name to x-api-key and paste your SendSurface Webhook Verification Secret / Token into the Value field.
  7. Click Create to save the connection.
Suggested Connection Name
sendsurface-ses
API Key Header Name
x-api-key

Step 3: Create an Amazon EventBridge API Destination

  1. Still under Amazon EventBridge → API destinations, switch to the API destinations tab and click Create API destination.
  2. Enter a name such as sendsurface-webhook.
  3. Paste the Webhook Endpoint URL you copied from SendSurface in Step 1 into API destination endpoint.
  4. Set HTTP method to POST.
  5. Under Connection, select Use an existing connection and pick sendsurface-ses.
  6. Set an invocation rate limit per second that comfortably covers your peak campaign volume (for example 50–300 requests/sec), then click Create.
Suggested API Destination Name (HTTP Method: POST)sendsurface-webhook

Step 4: Create an Amazon SES Configuration Set

  1. Open Amazon SES in the AWS Management Console (same region as your EventBridge resources).
  2. In the left sidebar under Configuration, click Configuration sets → Create set.
  3. Name your configuration set (for example sendsurface-ses-events) and click Create set.
Suggested Configuration Set Namesendsurface-ses-events

Step 5: Add Amazon EventBridge as an Event Destination

  1. Open your newly created Configuration Set (sendsurface-ses-events) and go to the Event destinations tab.
  2. Click Add destination.
  3. Select the event types you want SendSurface to track:
    • Deliveries (Delivery)
    • Hard bounces & Soft bounces (Bounce)
    • Opens (Open)
    • Clicks (Click)
    • Delivery delays (DeliveryDelay)
    • Rendering failures (Rendering Failure)
    • Subscriptions (Subscription)
  4. Click Next, select Amazon EventBridge as the destination type, enter a destination name, and select the Default EventBridge event bus (default).
  5. Review and click Add destination.

Step 6: Create an Amazon EventBridge Rule to Forward SES Events

  1. Return to Amazon EventBridge → Rules and ensure the default event bus is selected.
  2. Click Create rule, name it (e.g., forward-ses-to-sendsurface), and choose Rule with an event pattern.
  3. Under Event source, select AWS events or EventBridge partner events, then under Creation method choose Custom pattern (JSON editor) and paste the pattern below.
  4. In Select target(s), choose EventBridge API destination, select sendsurface-webhook, allow AWS to create a new IAM execution role for invoking the destination, and create the rule.
EventBridge Custom Event Pattern JSON:
{
  "source": ["aws.ses"]
}

Step 7: Attach the Configuration Set to Your Amazon SES Sending

Amazon SES only publishes events to EventBridge when outgoing messages reference your Configuration Set. Choose either method below:

Option A (Recommended): Set as Identity Default

In Amazon SES → Verified identities, open your sending domain or email address, open the Configuration set tab, click Edit, assign sendsurface-ses-events as the default configuration set, and save. Every SMTP campaign sent via SendSurface will emit events automatically.

Option B: Custom Email Header

When sending custom API or SMTP messages outside an identity default, include the X-SES-CONFIGURATION-SET header:

X-SES-CONFIGURATION-SET: sendsurface-ses-events

Step 8: Test and Verify the Integration

  1. In SendSurface Webhooks → Email Providers → SendSurface, click the Test button on your Amazon SES integration to confirm the webhook adapter records a simulated DELIVERED event.
  2. Send a test campaign or test email from SendSurface through your Amazon SES SMTP connection to a real mailbox you control.
  3. In AWS Console → Amazon EventBridge → Rules, inspect your rule's Monitoring metrics to confirm Invocations increase with zero FailedInvocations.
  4. In SendSurface Webhooks and Reports, verify that confirmed delivery and bounce/open/click metrics update cleanly.

Security Best Practices & Notes

  • SendSurface compares the x-api-key header value against your workspace verification secret using constant-time validation and returns 401 Unauthorized if missing or mismatched.
  • Never commit your Webhook Verification Secret / Token to source control or share it in public documentation.
  • Always configure your EventBridge API Destination with an https:// SendSurface URL so payloads and secrets remain encrypted in transit.
  • If a token is ever rotated in SendSurface, update the matching secret value in your EventBridge Connection immediately so AWS does not trigger 401 delivery failures.

Amazon SES EventBridge Frequently Asked Questions

Zero Markup · Your SMTP · Full Deliverability Control

Ready to Send High-Performance Campaigns?

Join high-volume senders, SaaS founders, and growth teams who trust SendSurface to orchestrate their email marketing.

Contact Support