Setup

info

This is a feature only available in the pro plans of the Pixel Manager for WooCommerce purchased on sweetcode.com. It is not available in the woocommerce.com version of the plugin.

This guide walks you through activating the Server-Side Proxy from start to finish. The process involves creating a SweetCode Cloud account, setting up a proxy domain, configuring DNS, and connecting it to the Pixel Manager.

Prerequisites

Before you begin, make sure you have:

• Pixel Manager for WooCommerce Pro installed and activated (version 1.57.0+)
• At least one server-side destination configured in the Pixel Manager (e.g. a Meta CAPI access token and pixel ID, a TikTok Events API token, etc.)
• DNS access to the domain where your WooCommerce shop is hosted
• A valid email address to sign up for SweetCode Cloud

Step 1: Create a SweetCode Cloud Account

1. Go to portal.sweetcode.cloud
2. Enter your email address and click Sign In
3. Check your inbox for the magic link and click it to access the dashboard

SweetCode Cloud uses passwordless authentication — no password to remember or manage.

info

A free plan is included by default. You can upgrade at any time if you need higher request limits.

Step 2: Add Your Domain in the Portal

1. In the SweetCode Cloud dashboard, navigate to Domains in the sidebar
2. Click Add Domain
3. Enter your shop's domain (e.g. yourshop.com)
4. Optionally customize the subdomain prefix (default: ssp, resulting in ssp.yourshop.com)
5. Click Add

The portal will show you the CNAME record you need to add in the next step.

Step 3: Configure DNS

Add a CNAME record in your domain's DNS settings:

Type	Name	Target
CNAME	ssp	ssp.sweetcode.cloud

Replace ssp with your chosen subdomain prefix if you customized it in the previous step.

Cloudflare Users: use DNS only, not Proxied

If your domain uses Cloudflare DNS, set the CNAME record's Proxy status to DNS only (grey cloud).

With Proxied (orange cloud) enabled, Cloudflare answers DNS queries with its own IP addresses and stops publishing the CNAME. As a result:

• the DNS verification in the SweetCode Cloud portal cannot see your record and reports it as missing,
• visiting ssp.yourshop.com returns Error 1014 — CNAME Cross-User Banned,
• the certificate validation never reaches SweetCode Cloud and eventually times out, which leaves the proxy domain stuck in Pending DNS.

DNS only costs you nothing here: ssp.sweetcode.cloud is already served from Cloudflare's edge network, so your events still take the fast path.

If you need to keep the record Proxied

Keeping the record proxied is possible — it is Cloudflare's Orange-to-Orange setup — but the certificate then has to be validated a different way.

In the SweetCode Cloud portal, open your domain, click Check DNS Status and choose Switch to TXT validation. The portal shows you a TXT record to publish, and your ssp record can stay orange.

Be aware of the trade-off: with the record proxied, your own Cloudflare zone handles every request first, so your WAF rules, Bot Fight Mode, rate limits and cache settings apply to tracking events before they reach SweetCode Cloud. A rule that challenges automated requests will silently drop events.

After adding the DNS record:

1. Go back to the SweetCode Cloud dashboard
2. Click Verify DNS on your domain

DNS propagation can take a few minutes. If verification fails, wait a few minutes and try again.

info

For detailed DNS instructions for specific registrars (Cloudflare, Namecheap, GoDaddy, Vercel, and others), see the SweetCode Cloud Domain Setup Guide.

Step 4: Connect the Pixel Manager

1. In the SweetCode Cloud dashboard, go to your domain and copy the Sync Token
2. In the Pixel Manager, open Server-Side → SweetCode Server-Side Proxy
3. Paste the sync token into the Sync token field
4. Click Activate

The Pixel Manager will:

• Validate the sync token with SweetCode Cloud
• Fetch your domain configuration
• Automatically push all configured destination credentials (pixel IDs and API tokens) to SweetCode Cloud

On success, the status panel will appear showing your connection status. No manual sync is needed — your destinations are pushed automatically during activation.

Important

After activation, flush all server-side caches on your WooCommerce site:

• Object cache (Redis, Memcached, etc.)
• Page cache (WP Super Cache, W3 Total Cache, LiteSpeed, etc.)
• Full-page caching at the hosting level (Cloudflare, Varnish, etc.)

The Pixel Manager needs to output updated JavaScript configuration to the frontend. Cached pages will still contain the old configuration until the cache is cleared.

Step 5: Verify

After activation and cache clearing, verify that everything is working:

1. Check the PMW status panel: In the Pixel Manager, open Server-Side → SweetCode Server-Side Proxy and confirm:

   • Routing Status shows Active
   • Config Status shows Synced
   • The overall status badge shows Active

2. Check the SweetCode Cloud portal: Navigate to Events > Live to see real-time event flow from your shop

3. Browse your shop: Visit a few product pages and add an item to the cart. Events should appear in the SweetCode Cloud portal within seconds.

tip

If you don't see events flowing, check the Management & Troubleshooting page for common issues and solutions.

What Happens After Activation

Once activated, the Server-Side Proxy works automatically:

• Browser events (PageView, ViewContent, AddToCart, InitiateCheckout, etc.) are routed through your first-party subdomain to SweetCode Cloud, which forwards them to the configured ad platform APIs.
• Purchase events are also routed through the proxy, with automatic fallback to direct sends if the proxy is unreachable.
• Config auto-sync keeps your credentials up to date — when you change a CAPI token or pixel ID in the Pixel Manager, the new credentials are automatically pushed to SweetCode Cloud. A daily sync also runs to ensure everything stays in sync.