Custom Events & Logs
Monitor your storefront events. Troubleshoot tracking triggers in real-time, capture customer account actions, and trace UTM parameters using TrakIt's built-in log debugger.
Captured Customer Actions
While standard checkouts track purchase cycles, TrakIt automatically intercepts and delivers secondary customer interaction triggers to feed email campaigns and cohort segments:
| Event Name | Trigger Action | Data Captured |
|---|---|---|
| login | Customer logs into their storefront Shopify account. | Customer ID / Email |
| signup | Customer registers a new account profile. | Hashed Profile Fields |
| email_subscribe | Customer joins a newsletter mailing list or subscription box. | Email Address / Scope |
TrakIt's Event Debugging & custom Actions Features
TrakIt includes specialized logging tools to audit marketing spend and configure custom storefront triggers:
Live Diagnostic Payload Debugger
TrakIt's dashboard includes a live debugger displaying incoming webhook records. View raw request headers, outbound server payloads, external API status codes (e.g. 200 OK or 400 Bad Request), and response bodies to diagnose setups immediately.
Real-Time UTM Attribution Parsing
When a checkout or action triggers, TrakIt parses URL parameters to isolate the original traffic referrer. It joins utm_source, utm_medium, and utm_campaign directly to backend order logs, ensuring clean multi-touch attribution reporting.
Custom JavaScript Event Handlers
Need to track video views, slider clicks, or custom banner taps? TrakIt lets you write custom storefront scripts that catch specific CSS selectors and push those interaction metrics straight into your GTM container as custom data layer triggers.
First-Party Payload Hashing
To remain compliant with customer privacy guidelines, TrakIt's server handles PII data scrubbing. Hashed email criteria, phone mappings, and customer metadata are automatically masked on-the-fly inside the edge handlers prior to transmission.
Payload Retention Policy
By default, diagnostic event payloads and logs are retained for **30 days**. This provides ample time to verify new campaign tags and test storefront variables before logs are archived.