Internal Enablement- Subdomains

THROW ME IN COACH

100

Can a customer set up multiple sending subdomains under a single Hive brand?

Yes—but it’s not enabled by default. An admin needs to turn it on in Django:

https://app.hive.co/admin/event/tour/

Important notes / limitations

1. Unsubscribe scope: If a contact unsubscribes, they’re unsubscribed from the entire brand—across all subdomains.

2. Reporting today: The platform doesn’t currently isolate metrics by subdomain. For example, the Analytics page aggregates data across all domains within the brand.

3. Tagging helps: With campaign tagging, it’s easier to attribute email/SMS to a specific brand (and you can adopt a tag convention per subdomain to approximate subdomain-level views until native filtering is available).

200

How long does DNS verification usually take before my subdomain is fully configured?

DNS verification usually completes within minutes to a few hours; allow up to 24–48 hours for full propagation.

If it’s still pending after 48 hours, there’s likely a configuration issue.

300

Which DNS records must a customer add to properly configure a custom sending subdomain?

Add 4 DNS records (not files): 2 CNAME + 2 TXT

• CNAME #1 — DKIM key
  Authenticates mail from your subdomain (e.g., s1._domainkey.send.yourdomain.com → vendor).

• CNAME #2 — Tracking domain
  Enables click/open tracking (e.g., link.yourdomain.com → vendor).

• TXT #1 — SPF
  Authorizes your email provider to send on your behalf (prevents spoofing).

• TXT #2 — DMARC
  Protects your domain from phishing/abuse and tells receivers how to handle failures.

WARM ME UP

100

What is the initial send increment when Hive starts sending from a custom subdomain?

200

200

What increment do we increase the sends from your subdomain?

The daily send cap doubles each day during warmup: Day 1 → 200, Day 2 → 400, Day 3 → 800, and so on.

Internal tool to help plan a customers warmup period: https://docs.google.com/spreadsheets/d/1M1uXCWrQGk2toDiTSo4_pkZjKlQ7J5CesGfaKvP2JyM/edit?gid=1620530889#gid=1620530889

300

How does Hive decide which contacts to route through my subdomain?

Early sends are random. As warmup progresses, routing adapts based on engagement: engaged contacts are sent via your custom subdomain, while less-engaged contacts are sent via Hive’s shared domains.

Product request: Instead of starting blind, add first-send logic that prioritizes contacts with recent purchase history (and/or recent engagement) on the custom subdomain to accelerate warmup and build reputation faster.

MAKE ME SING

100

Once a subdomain has been fully warmed up, does that ensure that all emails moving forward will be sent from their custom subdomain?

Short answer: No—the warmup cap is set by a backend rule and doesn’t auto-adjust.

What that means

• If you target more contacts than your current cap, Hive will send up to the cap on your custom subdomain; the overflow may route via Hive’s shared subdomain (or be held, depending on settings).
• If you don’t keep a steady cadence, your allowable send volume on the custom subdomain can decrease.

200

Name three ways a customer can improve email deliverability.

Targeting & Segmentation

Sending Cadence & Volume

List Hygiene

Content & Creative

Infrastructure & Authentication

300

Why are automated welcomes, contest/presale confirmations, and abandoned-checkout/buyer follow-ups so powerful for domain reputation?

They reach people at peak intent. These messages earn higher opens, clicks, and replies—and fewer spam complaints—sending strong positive signals to

 Gmail/Outlook/Apple. That lifts your sender (domain) reputation and improves inbox placement for future campaigns.