Getting Started

SweetCode Cloud is a server-side proxy for WooCommerce that routes tracking events through Cloudflare’s edge network. Instead of loading third-party scripts on your storefront, events flow server-side — improving page speed, protecting customer privacy, and increasing data accuracy.

Prerequisites

• A WooCommerce store with admin access
• Access to your domain’s DNS settings
• A SweetCode Cloud account

Quick Start

1. Create an account

Sign in at portal.sweetcode.cloud using your email. You’ll receive a magic link — no password needed.

2. Add your domain

Navigate to Domains in the dashboard and add your WooCommerce store domain (e.g. yourshop.com).

3. Configure DNS

Create a CNAME record for your proxy subdomain pointing to our edge:

ssp.yourshop.com → ssp.sweetcode.cloud

Your DNS provider’s dashboard will have an option to add records. Set:

Type	Name	Target	TTL
CNAME	ssp	ssp.sweetcode.cloud	Auto

4. Connect Pixel Manager

In the SweetCode Cloud dashboard, go to Domains → [your domain] and copy your Sync Token. Then in your WooCommerce admin, navigate to Pixel Manager → Settings and paste the token into the SweetCode Sync Token field.

Once saved, Pixel Manager automatically syncs your configured destinations (Google Analytics 4, Meta Conversions API, TikTok Events API, Reddit CAPI, etc.) to SweetCode Cloud — no manual setup needed.

Caution

After saving, flush all server-side caches in your WooCommerce store (e.g. object cache, page cache, or any full-page caching plugin). This ensures the updated Pixel Manager configuration — including the new proxy settings — is output to the front end so the Pixel Manager JavaScript library picks up the new SSP endpoint.

5. Start tracking

Once DNS propagates (usually within a few minutes) and caches are cleared, events sent to ssp.yourshop.com/v1/events are processed at the edge and forwarded to your configured destinations.

Next Steps

• Configuration guide — fine-tune proxy behavior and event routing
• Domain setup — detailed DNS configuration for various providers
• API reference — endpoints, authentication, and event schemas