Events & Tracking

SweetCode Cloud gives you full visibility into every tracking event flowing through the proxy. The Events page in the dashboard lets you monitor events in real time, filter by multiple criteria, and debug issues with specific destinations.

How Events Flow

Browser pixels vs. Conversion APIs

SweetCode Cloud handles server-side Conversion API calls — the HTTP requests your WooCommerce server would otherwise make to ad platform APIs. It does not replace browser-side pixels (JavaScript tags like Meta Pixel or TikTok Pixel), which fire directly from the visitor’s browser and don’t affect your server. Both work together for optimal tracking accuracy.

When a visitor interacts with your WooCommerce store, the event flow looks like this:

1. Browser — The visitor performs an action (page view, add to cart, purchase)
2. Pixel Manager JS — The Pixel Manager for WooCommerce JavaScript library captures the event and sends it to your proxy subdomain (ssp.yourshop.com/v1/events)
3. Cloudflare Edge — The SweetCode Cloud Worker at the nearest of 300+ edge locations receives the event
4. Validation — The Worker verifies the domain, checks quota, validates the payload, and verifies the request authenticity
5. Fan-out — The event is forwarded simultaneously to all configured destinations (Meta, TikTok, Pinterest, Snapchat, Reddit)
6. Response — Each destination’s API response is logged for debugging

This entire flow happens in milliseconds — your WooCommerce server is never involved in the server-side API calls.

Supported Event Types

SweetCode Cloud supports 9 standard event types that map to all supported ad platforms:

Event	Description	Typical Trigger
PageVisit	General page view	Any page load
ViewContent	Product or content page view	Product page
Search	Search query	Store search
AddToCart	Item added to cart	Add-to-cart button click
AddToWishlist	Item added to wishlist	Wishlist button click
Purchase	Completed order	Order confirmation page
Lead	Lead form submission	Contact or inquiry form
SignUp	Account registration	Account creation
Custom	Custom event	Any custom event (passed through)

Each event type is automatically mapped to the correct platform-specific event name for each destination. See the Supported Destinations guide for the full mapping table.

Purchase Events

Purchase events are not proxied through SweetCode Cloud. They are sent directly by the WooCommerce server via Pixel Manager’s built-in server-side tracking. This is by design for two reasons:

1. Order-specific data — Purchase events require detailed order information (line items, totals, tax, transaction IDs) that only the WooCommerce server knows. Routing these through the proxy would add complexity without benefit.
2. No load reduction — The WooCommerce server is already processing the order (payment, inventory, emails), so sending the conversion API call from the server adds negligible overhead. The SSP’s value is offloading the high-volume browsing events (page views, add-to-cart, etc.) that occur far more frequently.

All other event types are proxied through SweetCode Cloud.

Using the Events Page

The Events page in the dashboard has two viewing modes:

Live View

The Live tab shows events arriving in real time with automatic 2-second polling. A green pulsing indicator shows that live tracking is active. This is the best way to verify your setup is working — open your store in another browser tab, perform an action, and watch the event appear within seconds.

You can pause live tracking by clicking the indicator toggle.

Log View

The Log tab shows a paginated, filterable history of all events. Use this for investigating specific issues, reviewing past events, or auditing tracking accuracy.

Filtering Events

Both views support the following filters:

Filter	Description
Domain	Filter by a specific domain (useful if you have multiple stores)
Destination	Show events for a specific platform (Meta, TikTok, etc.)
Outcome	Filter by success or failure
Event Type	Filter by event type (Purchase, AddToCart, etc.)
Request ID	Search for a specific request by its unique ID
Time Range	Filter by time period (last hour, last 24 hours, etc.)

Note

Available time ranges depend on your plan’s log retention period. The Free plan retains logs for 1 hour, so only the “Last hour” time range is available. Upgrade to a paid plan for longer retention — up to 30 days on the Scale plan.

Understanding Event Outcomes

Each event in the log shows an outcome for each destination it was forwarded to:

Outcome	Meaning
Success	The destination API accepted the event
Failed	The destination API returned an error (check details for the error message)
Rate Limited	The request was rate-limited by SweetCode Cloud (120 req/IP/min)
Denied	The event was rejected before forwarding (quota exceeded, invalid payload, etc.)

Debugging Failed Events

When an event fails, click on it (or expand the row in table view) to see:

• The error message from the destination API
• The HTTP status code returned
• The request ID for cross-referencing
• The event type and destination involved

Common failure reasons:

• Invalid access token — Your destination API credentials may have expired. Regenerate them in the ad platform and update your Pixel Manager configuration
• Invalid pixel/account ID — Double-check the pixel or account ID in Pixel Manager
• Rate limiting by the destination — The ad platform is temporarily rejecting requests (usually resolves automatically)

Domain Events Preview

Each domain’s detail page (Domains → [your domain]) includes a compact event preview section showing the most recent events for that specific domain. This is a quick way to check if events are flowing without navigating to the full Events page.

Event Data

Each event sent through SweetCode Cloud can include:

User Data

Customer identifiers used for matching across platforms:

• Email — Hashed before sending to destinations
• IP Address — Used for geographic matching
• User Agent — Browser identification
• Click IDs — Facebook click ID (fbc) and browser ID (fbp)
• External ID — Your system’s customer identifier

Custom Data

Event-specific data:

• Currency and Value — Transaction amount (required for purchase events)
• Order ID — Your WooCommerce order ID
• Content IDs — Product SKUs or IDs
• Contents — Product details (name, price, quantity, category)
• Search String — The search query (for search events)

All of this data is automatically populated by Pixel Manager for WooCommerce — you don’t need to manually construct event payloads.

Log Retention

Event logs are retained based on your plan:

Plan	Retention
Free	1 hour
Pro	3 days
Business	7 days
Scale	30 days

After the retention period, event logs are permanently deleted. The logs are used only for your debugging and monitoring purposes.