SurveySparrow Custom Domains: How They Work & What to Know [2026]

Quick answer: Yes. SurveySparrow supports custom domains, and the setup is genuinely self-serve: add your domain under Settings → Account Settings → Domain, add the generated CNAME record at your domain provider, and click Verify Records—SSL is added automatically once verification succeeds. Survey URLs become surveys.acme.com/your-slug, with the slug customizable per survey.

Two documented constraints shape the feature, though. First, new custom domains are CNAME-only: SurveySparrow’s documentation states that mapping a domain directly to an IP address (an A record) is no longer supported for new setups—which, since standard DNS doesn’t allow CNAME records at a zone apex, effectively excludes bare domains like acme.com. Second, the custom domain is account-level: once configured, it applies to all surveys in the account, cannot be set differently per survey, and there’s no per-survey option to bypass it and use the default yourcompany.surveysparrow.com domain. Multi-brand setups need separate accounts—one per domain.

In this guide, we’ll walk through how the setup works, what it does well, and the documented limitations—plus how the feature compares if you’re evaluating branded-form platforms.

Yes. By default, every SurveySparrow survey link uses your account’s subdomain on SurveySparrow’s domain—yourcompany.surveysparrow.com. The Custom Domain feature replaces that with a web address you own, configured through your account settings without a sales conversation.

Here’s the landscape:

The CNAME-only policy is worth pausing on, because it defines what’s possible. SurveySparrow’s documentation states it directly: “SurveySparrow now supports custom domains only via CNAME records. Mapping your domain directly to an IP address (A record) is no longer supported for new custom domain setups.” Existing configurations keep working, but every newly connected domain must go through CNAME. And because a CNAME record can’t normally sit at a domain’s apex, the practical effect is that new SurveySparrow custom domains are subdomains—surveys.acme.com, not acme.com itself. If your website already lives at your root domain (as most do), that’s likely how you’d set it up anyway—but the apex option is off the table by policy, not just by DNS convention.

One more structural note: the custom domain applies to the account, and per the documentation, “the domain/subdomain portion of the survey URL cannot be removed entirely, as it is a required component of the URL structure.” What you customize per survey is the slug—the part after the domain.

Here’s the documented process:

1. Add the domain in SurveySparrow. Sign in, and from your account home page go to Settings. Under Account Settings, navigate to the Domain section and click Add Custom domain. Enter the domain URL of your choice and click Confirm.

2. Note the CNAME details. SurveySparrow shows you the TYPE, NAME, and VALUE for the DNS record. The value follows a standard format that depends on your account’s data-center region—custom-domain-region.surveysparrow.com:

3. Add the CNAME record at your domain provider. In your provider’s DNS management settings, add a new record of type CNAME, with the Name/Host from your SurveySparrow account and the region-specific Value as the target. If your host asks for a TTL, SurveySparrow suggests a value between 30 minutes and 1 hour—or leave it at the default. The exact steps vary by provider; the record itself is the same.

4. Verify. Back in your SurveySparrow account, click Verify Records. Allow buffer time for the configuration to propagate through your DNS host—once verification succeeds, the domain shows a Verified label.

If verification doesn’t detect your record, SurveySparrow’s troubleshooting guidance covers the usual causes: the CNAME was added to the wrong DNS zone (it belongs under the root domain—for feedback.acme.com, the record goes under acme.com), the record isn’t publicly resolvable, or propagation hasn’t finished yet. If it still fails, their support team will review a screenshot of the record from your provider.

5. SSL is automatic. Once the domain is verified, SurveySparrow adds the SSL certificate automatically from their end—no further action needed.

6. Point surveys at the domain. Your surveys now use the custom domain. To customize the path of an individual survey, edit the survey URL slug (the part after the domain) from Survey settings → Survey URL.

The feature works, and the setup is self-serve. These are the documented constraints:

• CNAME-only for new domains. A-record mapping is no longer supported for new custom domain setups. Since CNAME records can’t normally sit at a zone apex, new domains are effectively subdomains—surveys.acme.com, not acme.com. Legacy A-record configurations are grandfathered, but there’s no apex path for anyone connecting a domain today.
• The domain is account-level, with no bypass. Once a custom domain is added and verified, it applies to all surveys in the account. Per the documentation, it cannot be set differently for individual surveys, and there is no per-survey option to keep a specific survey on the default SurveySparrow domain. Every survey in the account moves to the custom domain.
• Multi-brand means multiple accounts. If you need different company names or domains for different sets of surveys, the documented answer is separate accounts or workspaces—one per brand/domain. There’s no multi-domain option within one account.
• The region determines your CNAME value. The record’s target depends on where your account’s data center is located—seven regions, seven different values. It’s a lookup-table detail rather than a blocker, but it’s an extra failure mode: using the wrong region’s value means verification fails.
• No documented removal flow. SurveySparrow’s own documentation notes that it doesn’t cover removing or deleting a configured custom domain from an account—worth knowing before you connect one, since the off-ramp isn’t documented.

What works well: the flow is fully self-serve with no sales contact, the CNAME record is a single standard entry, SSL is issued automatically after verification with nothing to provision or renew on your end, per-survey slugs keep URLs readable (surveys.acme.com/customer-feedback rather than opaque IDs), and the troubleshooting guidance for failed verification is concrete. Within a single brand running surveys from one account, it’s a complete feature.

Let’s be honest about the overlap first: SurveySparrow’s custom domain implementation is legitimate. Both platforms run self-serve CNAME setup, both issue SSL automatically after verification, and both produce readable per-survey URLs—SurveySparrow via slugs, Formware via per-form path mapping. If you’re a single brand running everything from one account and you’re happy on a subdomain, SurveySparrow’s feature does the job.

The differences are in the flexibility around the feature:

Domain types. SurveySparrow’s CNAME-only policy for new setups means new domains are subdomains—apex domains aren’t part of the flow. Formware supports both: subdomains via CNAME records and apex domains via A records—so acme.com and ask.acme.com are both viable.

Per-survey control. This is the sharpest documented difference. On SurveySparrow, the custom domain applies to the entire account—every survey, no exceptions, no per-survey bypass back to the default domain, and different domains require separate accounts. Formware’s model is per-form: from the domain’s Configure screen, you map individual published forms to the paths you want—ask.acme.com/contact, ask.acme.com/customer-survey—so the URLs you brand are the forms you choose, and mapping management (including removal) lives in one screen.

Multi-brand architecture. SurveySparrow’s documented answer to multiple brands is multiple accounts—one per domain. Whether that’s a limitation depends on your setup: for a single-brand deployment it’s irrelevant; for an agency or a company running distinct brands, it’s an operational constraint that sits directly on top of the domain feature.

What surrounds the domain. A branded URL pays off most when the whole journey is branded and the platform supports the workflow behind it. Formware’s Pro bundles white-labeling (no badge, your logo and favicon), partial submissions so abandoned leads aren’t lost, per-ending custom redirects that hand respondents off to a booking page or checkout, and respondent email notifications—with full visual customization across colors, fonts, buttons, and backgrounds.

The pricing question. Formware’s Pro is $29.99/month or $299/year—published, the same for everyone, with custom domains included. SurveySparrow’s plans are structured around fixed response allowances per tier (reported at $19–$99/month across its self-serve tiers, with figures varying between sources), so costs scale with response volume—and per available comparisons, custom domains sit on its paid plans. The comparison to run: what does the plan you’d need cost, and what does the response allowance do when a campaign outperforms?

The free-plan math. Formware’s free plan offers unlimited forms, questions, and responses (subject to fair use), alongside hidden fields (pair them with the UTM builder for campaign tracking), recall, and conditional logic at no cost. Pro is the single step up—built for the branded layer: custom domains, white-labeling, and the lead-recovery workflow around them.

It’s also worth naming the positioning difference these pages sit inside: SurveySparrow is an experience-management platform—recurring feedback programs, multi-channel distribution, and CX reporting are its center of gravity. Formware is a dedicated form builder with a one-question-at-a-time experience, built for conversion. If your need is ongoing VOC programs, SurveySparrow’s platform may be worth its structure; if your forms are how customers reach you, the domain question is part of a bigger fit question.

If you’re weighing Formware against SurveySparrow more broadly—beyond just domains—we break down the full comparison, including the response-metering difference, in Formware vs. SurveySparrow.

Yes. SurveySparrow supports custom domains with self-serve setup: add the domain under Settings → Account Settings → Domain, add the generated CNAME record at your domain provider, and verify. SSL is added automatically once verification succeeds, and survey URLs become surveys.acme.com/your-slug. Two constraints apply: new domains must use CNAME records (A records are no longer supported for new setups), and the domain applies account-wide to all surveys.

Not for new setups. SurveySparrow’s documentation states that custom domains are supported only via CNAME records, and mapping a domain directly to an IP address (A record) is no longer supported for new custom domains. Because CNAME records can’t normally sit at a zone apex, new custom domains are effectively subdomains—surveys.acme.com, not acme.com. Existing A-record configurations continue to work but can’t be the model for new domains. Formware supports both: apex domains via A records and subdomains via CNAME on its custom domains feature.

Add the domain in Settings → Account Settings → Domain, note the CNAME details SurveySparrow generates, and add a CNAME record at your domain provider pointing your chosen subdomain at the value for your data-center region—it follows the format custom-domain-region.surveysparrow.com (US, EU, ME, AP, Sydney, Canada, and UK each have their own value). Back in SurveySparrow, click Verify Records. After verification, SSL is added automatically, and you can customize each survey’s path via Survey settings → Survey URL.

No. The custom domain is configured at the account level and applies to all surveys in that account—it can’t be set differently for individual surveys, and there’s no per-survey option to bypass it and use the default SurveySparrow domain. Per the documentation, if you need different domains for different sets of surveys, you’ll need to manage them in separate accounts or workspaces—one per brand/domain.

Yes. The survey URL slug—the part after the domain—is editable per survey from Survey settings → Survey URL. The domain portion itself is a required component of the URL structure and can’t be removed; what you customize is the slug that follows it.

Yes. Once your custom domain is verified, SurveySparrow adds the SSL certificate automatically—no purchase, upload, or renewal management on your end. Formware works the same way: certificates are issued after domain verification and renewed automatically.

SurveySparrow’s custom-domain documentation doesn’t publish a plan gate or a per-domain fee, and publicly available comparisons place the feature on its paid plans—verify against SurveySparrow’s current plan pages before committing. Its self-serve tiers are reported to run $19–$99/month, structured around fixed response allowances. Formware includes custom domains on Pro at $29.99/month or $299/year—published pricing, with domains included rather than gated.

That’s not covered in SurveySparrow’s documentation—the setup guide explicitly notes it doesn’t cover removing or deleting a configured custom domain. If you need to disconnect one, support is the documented channel. It’s worth knowing before you connect a domain, since the off-ramp isn’t self-documented.

Formware includes custom domains on Pro at $29.99/month or $299/year—published pricing, self-serve CNAME setup with automatic SSL, and per-form URL mapping so paths like ask.acme.com/contact are assigned form by form. It supports both apex domains and subdomains, and Pro bundles white-labeling, partial submissions, custom redirects, and respondent emails. Its free plan offers unlimited forms, questions, and responses—plus hidden fields, logic, and recall. See the full Formware vs. SurveySparrow comparison for the wider feature picture.

SurveySparrow’s custom-domain features and plan details were verified at the time of writing and may change. Check SurveySparrow’s site for current details before making a purchase decision.