Domain Setup

SweetCode Cloud uses a CNAME record to route traffic through Cloudflare’s edge network via a first-party subdomain on your domain. This guide covers setup for common DNS providers.

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 and forwarded to your configured ad-platform destinations.

Browser → ssp.yourshop.com → CNAME → ssp.sweetcode.cloud → Cloudflare Edge → Meta, TikTok, etc.

What to enter as your shop domain

When adding a domain in the dashboard, the Shop Domain field should be your root domain only — no www, no protocol, no path.

✅ Correct	❌ Incorrect
mydomain.com	www.mydomain.com
myshop.de	https://mydomain.com
example.co	mydomain.com/shop

The Subdomain Prefix (default: ssp) is combined with your shop domain to create the proxy endpoint — for example, ssp.mydomain.com. This is a new subdomain you create in your DNS settings; it is not your website URL.

Domain Limits

The number of domains you can add depends on your plan:

Plan	Max Domains
Free	5
Pro	25
Business	50
Scale	100

If you need more domains, upgrade your plan from the Billing page in the dashboard.

DNS Configuration

The Name field is just the subdomain prefix

When creating the CNAME record, the Name (or Host) field should be just the subdomain prefix — for example, ssp — not ssp.mydomain.com. Your DNS provider automatically appends your root domain.

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. Click Save

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

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)

1. Go to Domains → [your domain] → DNS Records
2. Add a CNAME record: Name ssp, Value ssp.sweetcode.cloud

Other Providers

For any other DNS provider, the process is the same — create a CNAME record with:

Field	Value
Type	CNAME
Name	ssp (or your chosen subdomain)
Target	ssp.sweetcode.cloud
TTL	Auto / Default

Verification

After creating the DNS record, verify it in two ways:

Dashboard Verification

Return to Domains → [your domain] in the SweetCode Cloud dashboard and click the Verify DNS button. If DNS has propagated, the routing status changes from Pending DNS to Active.

Command Line

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

By default, the proxy uses the ssp subdomain. You can customize this when adding the domain in the dashboard. Common alternatives:

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

The subdomain must be a valid DNS label (lowercase letters, numbers, and hyphens).

Troubleshooting

CNAME not resolving

• Ensure the record was saved (check for typos in the target — it must be exactly ssp.sweetcode.cloud)
• Wait at least 5 minutes for propagation
• Use dig or dnschecker.org to verify from multiple locations

SSL certificate errors

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

Domain stuck in “Pending DNS”

If the dashboard shows “Pending DNS” for more than 30 minutes:

1. Double-check the CNAME record target is exactly ssp.sweetcode.cloud
2. Try clicking Verify DNS again in the dashboard
3. Check for conflicting records — if an A record exists for the same subdomain, delete it before adding the CNAME

Domain limit reached

If you see a “domain limit exceeded” error when adding a domain, you’ve reached your plan’s limit. See the Billing & Plans guide to upgrade.

For more issues, see the full Troubleshooting guide.