Skip to content
SweetCode Cloud

Domain Setup

SweetCode Cloud uses a CNAME record to route traffic through the edge proxy. This guide covers setup for common DNS providers.

How It Works

Section titled “How It Works”

When you add a domain in the dashboard, SweetCode Cloud assigns a proxy subdomain (default: ssp). You create a CNAME record pointing that subdomain to ssp.sweetcode.cloud. All requests to ssp.yourshop.com are then processed by the edge proxy.

ssp.yourshop.com  →  CNAME  →  ssp.sweetcode.cloud  →  Cloudflare Edge

DNS Configuration

Section titled “DNS Configuration”

Cloudflare

Section titled “Cloudflare”
  1. Go to DNS → Records in your Cloudflare dashboard
  2. Click Add Record
  3. Set Type to CNAME, Name to ssp, and Target to ssp.sweetcode.cloud
  4. Set Proxy status to DNS only (gray cloud) — SweetCode Cloud handles its own edge routing
  5. Click Save

Namecheap

Section titled “Namecheap”
  1. Go to Domain List → Manage → Advanced DNS
  2. Click Add New Record
  3. Type: CNAME, Host: ssp, Value: ssp.sweetcode.cloud, TTL: Automatic
  4. Click the checkmark to save

GoDaddy

Section titled “GoDaddy”
  1. Go to My Products → DNS → DNS Records
  2. Click Add
  3. Type: CNAME, Name: ssp, Value: ssp.sweetcode.cloud, TTL: 1 Hour
  4. Click Save

Vercel (if using Vercel DNS)

Section titled “Vercel (if using Vercel DNS)”
  1. Go to Domains → [your domain] → DNS Records
  2. Add a CNAME record: Name ssp, Value ssp.sweetcode.cloud

Verification

Section titled “Verification”

After creating the record, verify propagation:

Terminal window
dig ssp.yourshop.com CNAME +short
# Expected: ssp.sweetcode.cloud.

DNS propagation typically takes 1–5 minutes but can take up to 48 hours in rare cases.

Custom Subdomains

Section titled “Custom Subdomains”

By default, the proxy uses the ssp subdomain. You can customize this in the dashboard under Domains → [your domain] → Settings. Common alternatives:

  • track.yourshop.com
  • data.yourshop.com
  • events.yourshop.com

Troubleshooting

Section titled “Troubleshooting”

CNAME not resolving

Section titled “CNAME not resolving”
  • Ensure the record was saved (check for typos in the target)
  • Wait at least 5 minutes for propagation
  • Use dig or dnschecker.org to verify

SSL certificate errors

Section titled “SSL certificate errors”

SweetCode Cloud automatically provisions TLS certificates via Cloudflare. This usually completes within minutes of DNS validation. If you see certificate errors, wait 15 minutes and try again.