Custom Domains

Replace the default JourneyFuse URLs with your own branded domain. Instead of sharing links like app.journeyfuse.com/portal/abc123, your clients see trips.youragency.com/portal/abc123 — reinforcing your brand at every touchpoint.

What changes: Portal links, proposal links, itinerary links, and invoice links will all use your custom domain once configured.

Setup Steps

Step 1: Choose Your Subdomain

Pick a subdomain on a domain you own — for example:

• trips.youragency.com
• travel.youragency.com
• portal.youragency.com

Important: Use a subdomain, not your root domain. Most DNS providers don't support CNAME records at the root (youragency.com). A subdomain like trips.youragency.com works with every provider.

Step 2: Add a CNAME Record

Log in to your DNS provider (GoDaddy, Namecheap, Cloudflare, Google Domains, etc.) and add a CNAME record:

Field	Value
Type	CNAME
Name / Host	Your subdomain prefix (e.g., trips)
Target / Points to	5ae12405124194fc.vercel-dns-016.com
TTL	Auto or 300

The exact target value is shown on the Settings → Domain page in JourneyFuse — always copy it from there to be safe. If you set up your domain before May 2026 and used the older cname.vercel-dns.com target, that still works; no need to change it.

Step 3: Configure in JourneyFuse

1. Go to Settings → Domain
2. Enter your full subdomain (e.g., trips.youragency.com)
3. Click Verify DNS

JourneyFuse will check that your CNAME record is pointing to the right place. If everything looks good, your domain is connected.

Step 4: Wait for Verification

DNS changes can take anywhere from a few minutes to 48 hours to propagate worldwide. If verification doesn't succeed immediately, wait and try again later.

Once verified, an SSL certificate is automatically provisioned for your domain — no extra steps needed. Your links will work over HTTPS right away.

Your Branded Landing Page

Once your custom domain is active, visitors to your root domain (e.g., trips.youragency.com) see a branded landing page featuring:

• Your logo and brand colors — pulled from your workspace branding settings
• Portal access code entry — clients can enter their access code directly to reach their portal
• Your bio and photo — if you've added an agent headshot and bio in workspace settings
• Travel specialties — displayed as badges if configured in your agency profile
• Lead capture form — optionally link one of your forms as a call-to-action button for new prospects

Configuring the Landing Page

The landing page automatically uses your existing branding (logo, accent color, agent photo, bio, social links). To add a lead capture form:

1. Go to Settings → Domain
2. Under Landing Page, select a form from the dropdown
3. Customize the button text (e.g., "Get a Free Quote" or "Plan Your Next Trip")
4. Click Save

The form link will appear as a prominent button on your landing page. If you don't select a form, the button won't appear — no empty state is shown.

Tip: Create a dedicated lead intake form for your landing page. This way, prospects who discover your domain can submit an inquiry without needing a portal access code.

Editing Section Text

Under Settings → Domain → Landing Page, you can also reword the section titles and rename the specialty cards. Every field is optional — leave one blank and the landing page keeps its default wording.

• Section Headings — override the titles and subtitles for the "Trips planned with extra care" (Specialties) and "Choose how to begin" (inquiry forms) sections.
• Specialty Cards — give each of the first three cards a custom name (for example, "River Cruises") instead of pulling the wording straight from your profile specialties.
• Show the "What I offer" section — this second list of your specialties appears once you have three or more specialties. Turn the switch off to hide it, or edit its title and subtitle when it's shown.

Click Save after making changes. Updates appear on your landing page right away.

This section sets the agency-wide default. Each advisor can also personalize their own landing page — including renaming the specialty cards and choosing their own call-to-action buttons — from Settings → My Landing Page. See Your Advisor Landing Page.

Site Visibility (Public vs. Private)

When you connect a custom domain, your site goes live right away — your landing page, your advisor pages, and your directory become reachable at your domain, and search engines like Google can index them. This is separate from the Enable public directory setting (that switch only controls the advisor directory listing, not whether your site is reachable at all).

If you're not ready for the world to see your site yet, you can make the whole thing private:

1. Go to Settings → Domain
2. Under Site visibility, turn the switch off

While your site is private, anyone who visits your domain — your landing page, your advisor pages, your directory, and your public supplier list — gets a not-found page instead, and search engines won't index it. Flip the switch back on whenever you're ready to launch.

Note: Your clients' existing links keep working even when your site is private. Portal, proposal, invoice, and itinerary links are private, per-client links, so taking your public site private never breaks a link you've already shared with a client.

Removing a Page Already in Google

Making your site private stops search engines from finding it going forward, but a page Google already indexed can linger in results until Google re-crawls it (which can take a while). To remove it faster, use Google Search Console: verify your domain, then use the Removals tool to request removal of the URL. Because the page now returns a not-found response, the removal becomes permanent on the next crawl.

Troubleshooting

"Could not resolve CNAME"

This usually means DNS hasn't propagated yet. Double-check that:

1. You added a CNAME record, not an A record or TXT record
2. The Name/Host field is just the subdomain prefix (e.g., trips), not the full domain
3. The Target matches the value shown on the Settings → Domain page (e.g., 5ae12405124194fc.vercel-dns-016.com). The older cname.vercel-dns.com target also still works.

If everything looks correct, wait 30 minutes and click Verify DNS again. Full propagation can take up to 48 hours in rare cases.

Cloudflare Users

If you use Cloudflare as your DNS provider, make sure the proxy is disabled for this record. Set the record to DNS only mode (grey cloud icon, not orange). Cloudflare's proxy intercepts traffic in a way that blocks domain verification.

Still Not Working After 48 Hours

• Confirm the CNAME record exists using a tool like dnschecker.org
• Make sure there isn't a conflicting A record on the same subdomain
• Contact support if the record resolves correctly but JourneyFuse still can't verify it