Skip to main content
A sending account is an email service you own that ElasticFunnels sends through. Besides your SMTP server, Mailgun, SendGrid and Mailrelay, you can connect four API services: Each key is checked with the provider when you save. A key that the provider refuses is not saved.

​
Where a sending account is used

Members area login codes and links are the exception. They are sent by your pages, which send only through brand SMTP, Mailgun, SendGrid or Mailrelay. Without one of those, ElasticFunnels sends the login email under your brand name, as it does today. A paused account sends nothing. For a ticket reply, the ticket source’s own SMTP server is used instead.

​
Connect Amazon SES

The Amazon SES sending account form: Access key ID, Region, Secret access key and Configuration set, with the setup steps beside it
1

Verify your domain in SES

In the SES console, open Identities and verify the domain you send from. Do this in the region you will pick below: each region has its own identities and limits.
2

Leave the SES sandbox

Request production access on the SES account dashboard. In the sandbox, SES only delivers to addresses you verified yourself.
3

Create an access key

In IAM, create a user with the ses:SendEmail and ses:GetAccount permissions, then create an access key for it.
4

Fill in the form

Go to Apps → Integrations, add Amazon SES, and paste the Access key ID and Secret access key. Pick the Region your domain is verified in. The secret is checked with SES when you save, stored encrypted and never shown again.
5

Add a configuration set

Type the name of an SES configuration set in Configuration set. It is applied to every email sent through this account. You need one to get opens, clicks and bounces back, as Delivery events explains.

​
Connect Postmark

A saved Postmark sending account: the server API token, the transactional and broadcast streams, and Delivery events turned on
1

Verify your sender

In Postmark, verify your sending domain under Sender Signatures.
2

Add a Broadcasts stream

On the server you send from, add a Broadcasts message stream if it has none. Postmark does not allow marketing email on a transactional stream.
3

Paste the server token

Open the server, copy a token from its API Tokens tab and paste it in Server API token.
4

Check the stream names

Transactional stream carries order and subscription emails. Postmark calls it outbound by default. Broadcast stream carries campaigns and defaults to broadcast. Change them only if your server uses other names.

​
Connect Brevo

Brevo uses one API key for everything. If you already connected Brevo to sync contacts, open that connection: the same key now sends email too.
  1. In Brevo, create an API key under SMTP & API. It starts with xkeysib-.
  2. To send email, add a sender or authenticate your domain under Senders & IP.
  3. Paste the key in API key, and optionally set a default sender that uses that verified address or domain.

​
Connect Resend

1

Verify your domain

In Resend, add and verify your sending domain under Domains.
2

Create an API key

Create an API key under API Keys and paste it in API key. It starts with re_. A key limited to sending is enough to send email.
3

Decide how events reach ElasticFunnels

With a full access key, ElasticFunnels adds the webhook for opens, clicks and bounces when you save. With a sending-only key, you add the webhook in Resend yourself and paste its signing secret. See Delivery events.

​
Default sender

Every account has a Default sender card: Default From Email, Default From Name and Default Reply-To Email. All three are optional. The address you use must be verified with that provider (a verified domain in SES or Resend, a confirmed sender signature or domain in Postmark, a sender or authenticated domain in Brevo), or the provider refuses the email.

​
How the sender is chosen

The Default sender card of a sending account with How the sender is chosen opened, listing the order: the send's own sender, this default, then the template's For each email sent through Amazon SES, Postmark, Brevo or Resend, the from address comes from the first of these that is set:
  1. A sender set on the send itself. A campaign’s own from address, a ticket reply’s Reply with Email, or the From email typed on an automation’s Send email step.
  2. The account’s Default From Email.
  3. The email template’s from address.
If none of the three is set, the email is not sent and the error asks you to set a default from email on the account or on the email. The from name follows the address. When the send sets its own sender, its name is used. Otherwise the account’s Default From Name is used, and the template’s name only when the account has none. Reply-to works the other way round. The reply-to on the email itself (the campaign’s, or the template’s for an order email) is used first, and the account’s Default Reply-To Email only when the email has none. When the brand sends over SMTP instead, the sender on the SMTP settings is used for every email. See Sending Setup.