FAQ

Frequently asked questions about the Server-Side Proxy.

Which events are proxied?

All browser-originated server-side events are routed through the proxy. This includes:

• PageView
• ViewContent (product page views)
• AddToCart
• InitiateCheckout
• Search
• Subscribe
• And other non-purchase e-commerce events

Purchase events are also routed through the proxy. If the proxy is unreachable, purchase events automatically fall back to direct sends from your WooCommerce server on a per-platform basis, ensuring no revenue data is lost.

Why isn't GA4 proxied?

Google Analytics 4 (GA4) Measurement Protocol only sends purchase events server-side. Since GA4 doesn't send browser-originated events through a server-side API (it uses gtag.js exclusively for those), there is nothing to proxy. The Pixel Manager continues to handle GA4 purchase events directly.

What happens if the proxy goes down?

This depends on your Proxy Failure Behavior setting:

• Fall back to PMW internal event router (default): The Pixel Manager sends events directly from your WooCommerce server. No data is lost — you temporarily lose the performance benefit, but tracking continues uninterrupted.
• Drop server-side events: Events are silently dropped until the proxy recovers.

The default fallback option is recommended for most shops.

Is my data secure?

Yes. Your ad platform credentials (CAPI tokens, pixel IDs) are:

• Transmitted over HTTPS (TLS 1.3)
• Encrypted at rest in SweetCode Cloud using AES-GCM encryption
• Never logged or exposed in plaintext
• Masked in the SweetCode Cloud portal UI (only last 4 characters are shown)

For full details, see the SweetCode Cloud Security & Privacy documentation.

How do I update my CAPI tokens?

Just update them in the Pixel Manager settings as you normally would. The Server-Side Proxy automatically detects credential changes and pushes the updated configuration to SweetCode Cloud. No manual sync is needed — though you can always click Sync Now to force an immediate update.

Do I need to change anything in the ad platform dashboards?

No. The Server-Side Proxy is transparent to the ad platforms. Events arrive at their APIs in the same format as they would from a direct server-side send. Your existing pixel configurations, audiences, and campaigns continue to work without changes.

Can I use the proxy with only some platforms?

The Server-Side Proxy proxies events for all destinations that have a CAPI token and pixel ID configured in the Pixel Manager. If you only have Meta CAPI configured, only Meta events will flow through the proxy. There is no per-platform toggle — the proxy handles whatever destinations are active.

Does the proxy affect browser-side pixel tracking?

No. Browser-side tracking (JavaScript pixels) continues to work independently. The Server-Side Proxy only handles the server-side component of event tracking (Conversion APIs). Both browser and server events are still sent with proper deduplication event IDs.

What is the free plan limit?

SweetCode Cloud includes a free tier with a limited number of monthly events. You can view the current plan limits on the SweetCode Cloud pricing page. If you exceed the free plan limit, events may be dropped until the next billing cycle or until you upgrade.

Can I use a custom subdomain?

Yes. The default subdomain prefix is ssp (resulting in ssp.yourshop.com), but you can customize it when adding your domain in the SweetCode Cloud portal. For example, you could use data.yourshop.com or track.yourshop.com.

Can I use the proxy with multiple domains on a single WordPress install?

Yes. If your single WordPress installation serves multiple domains (without WordPress Multisite), you can connect each domain to its own SSP proxy endpoint. This requires:

1. Creating a separate domain in the SweetCode Cloud portal for each additional domain
2. Adding the pmw_ssp_additional_domains filter to your child theme's functions.php

The Pixel Manager will automatically output the correct proxy URL for visitors on each domain and keep all domains synced with your CAPI configuration.

See the SSP Additional Domains filter documentation for setup instructions.

I upgraded my plan but events still aren't going through the proxy. Why?

After upgrading (or after the billing cycle resets), the Pixel Manager needs to learn that the quota is no longer exceeded. This happens via a sync — either automatic (daily at 3:15 AM, or triggered by SweetCode Cloud) or manual (save your Pixel Manager settings or click Sync Now).

However, even after a successful sync, page caches on your WooCommerce site may still serve stale HTML that contains the old quota_exceeded flag. This is the most common reason the proxy doesn't resume after a quota recovery.

Additionally, the Pixel Manager's JavaScript stores the SSP state in the browser's sessionStorage. Visitor sessions that already encountered the quota-exceeded state will continue using fallback for the rest of that tab's session. This resolves automatically when visitors open new tabs — no manual action is needed.

To restore proxy routing:

1. Trigger a resync (save settings, click Sync Now, or wait for auto-sync)
2. Flush all page caches (caching plugin, hosting cache, CDN, Cloudflare, Varnish)
3. Verify in a new browser tab by checking the Network tab for requests to your proxy subdomain

See the Quota Exceeded troubleshooting section for the full recovery checklist.

Does the proxy work with Cloudflare?

Yes. If your domain uses Cloudflare DNS, you need to set the CNAME record to Proxied (orange cloud enabled). See the Setup Guide for details.