Setup guide

Connect Brevo and your domain to send campaigns from My Hot Lead

My Hot Lead sends email through your own Brevo account. You add an API key, verify your domain for deliverability, and (optionally) register a webhook so the app can show delivery and open statistics. This guide walks through each step, including typical cPanel DNS screens.

Overview

Typical order of work:

  1. Create a Brevo account (or sign in).
  2. Copy your API v3 key into My Hot Lead → My Account.
  3. Add the app server’s outbound IP under Brevo Authorised IPs (required if Brevo enforces IP allowlisting for your key).
  4. Add and authenticate your sending domain in Brevo, then create the DNS records (often in cPanel → Zone Editor).
  5. Set your sender / From address in My Hot Lead to match an authenticated sender in Brevo.
  6. Paste the app’s webhook URL in Brevo so opens and deliveries sync to your dashboard.

DNS changes can take from a few minutes up to 48 hours to propagate. Brevo’s own domain verification screen is the source of truth for whether SPF/DKIM are valid.

Create or open your Brevo account

If you do not use Brevo yet, sign up at brevo.com. Choose a plan that fits your sending volume (transactional and marketing features may depend on your Brevo subscription).

Complete Brevo account verification (email, company details) as prompted so API and sending features are enabled.

API key

In Brevo, open SMTP & API → API keys (or go directly to API keys in Brevo).

  1. Create a new key with permission to send emails and manage webhooks as needed, or use an existing key.
  2. Copy the key (it often starts with xkeysib-).
  3. In My Hot Lead, go to My Account, find Brevo (sending), paste the key into Brevo API Key, and click Save.

Keep the key secret. If it leaks, revoke it in Brevo and create a new one.

Authorise the server IP in Brevo

My Hot Lead calls Brevo’s API from a fixed outbound IP. Brevo can reject requests from unknown IPs until you allowlist that address.

  1. In My Hot Lead → My Account → Brevo (sending), note the Outbound IP shown after you save your API key (or ask your host if the app displays a placeholder).
  2. In Brevo, open Security → Authorised IPs (direct link).
  3. Add the IP, save, and wait a minute. Refresh My Hot Lead; the “Authorised IP in Brevo” status should turn green when the check passes.

Domain, sender, and DNS (SPF / DKIM)

To send as you@yourdomain.com, Brevo must authenticate your domain. That usually means adding DNS records provided by Brevo (SPF and DKIM, sometimes a verification TXT record).

1. Add the domain in Brevo

In Brevo, open Senders & IP → Domains (wording may vary slightly). Add your root domain or subdomain, then start domain authentication. Brevo will show the exact DNS records to create.

2. Add records in cPanel (typical)

  1. Log in to the control panel your host provides (often cPanel).
  2. Open Zone Editor (sometimes under Domains).
  3. Select your domain, then choose Manage or Add record.
  4. For each record Brevo shows, add:
    • Type: usually TXT; DKIM may be a TXT on a Brevo-specific hostname (e.g. mail._domainkey or a long selector).
    • Name / Host: paste exactly as Brevo specifies (cPanel often appends your domain; if Brevo gives a full hostname, follow your host’s help doc to avoid doubling the domain).
    • Value: paste the full string from Brevo (no quotes unless your DNS UI requires them).
    • TTL: default (e.g. 14400) is fine.
  5. Save each record. Repeat for SPF (if Brevo asks you to merge or replace an existing SPF TXT, only one SPF TXT should exist for a given zone—merge includes into a single v=spf1 ... ~all line).

3. Verify in Brevo

Return to Brevo’s domain page and click verify / refresh. When DKIM and SPF pass, you can send from addresses on that domain (subject to sender confirmation rules inside Brevo).

4. Not using cPanel?

The same records work in Cloudflare, Route 53, GoDaddy, or any DNS provider—only the UI differs. Always copy names and values exactly from Brevo.

Sender settings in My Hot Lead

In My Account:

  • Profile: set Sender name, Sender email, and optional Reply-to. These should match a verified sender/domain in Brevo.
  • Brevo (sending): optional From email (sender) override; if empty, the profile sender email is used.

If Brevo rejects a send because the sender is not verified, fix domain authentication or use a sender address Brevo already validated.

Webhook (delivery & open tracking)

My Hot Lead exposes a single webhook URL for your account. Brevo will POST events to it when you register the URL in their dashboard.

  1. In My Hot Lead → My Account → Brevo (sending), copy the Webhook URL value (format: https://app.myhotlead.com/webhook/brevo/ with your account’s path as shown in the app).
  2. In Brevo, open webhooks / transactional settings (Brevo webhooks area — exact menu may vary).
  3. Create a webhook pointing to that URL. Enable event types you care about (e.g. delivered, opened) per Brevo’s options.
  4. Save. After sends run, your My Hot Lead dashboard can reflect delivery and opens if the integration is configured correctly on both sides.

The webhook must be reachable from the public internet and use HTTPS.

Troubleshooting

  • “Unrecognised IP” or API errors: confirm the outbound IP is in Brevo → Authorised IPs and that your API key is active.
  • Invalid sender / domain: re-check Brevo domain authentication and that the From address uses that domain.
  • DNS not verifying: confirm TXT records match Brevo exactly; check for duplicate SPF TXT records; allow propagation time.
  • No opens or deliveries in the app: confirm the webhook URL in Brevo matches My Hot Lead exactly and that events are selected.

For product support, contact the email listed on the Legal Notice page.