Debug Logging

Debug logging is a built-in diagnostic system that records what your Tracksies plugins are doing behind the scenes — order syncs, email sends, tag calculations, review submissions, report generation, lead scoring, and more — so when something goes wrong, you can see exactly what happened and when.

Unlike most WordPress plugins that dump everything into WordPress’s debug.log, Tracksies gives each plugin its own isolated, dedicated log file. You toggle logging on or off per-plugin from the admin, with no code changes and no editing wp-config.php. Each plugin’s log only shows that plugin’s activity, so you never have to wade through thousands of lines of unrelated noise to find what matters.

—

Why This Matters

Most WooCommerce stores have 20+ active plugins. When something breaks and you open debug.log, you’re staring at a 50MB file full of deprecation notices, third-party errors, and random chatter from plugins you’ve never heard of. Finding the one line about your failed order sync is like searching for a needle in a haystack — blindfolded.

Tracksies takes a different approach:

• Per-plugin isolation — Each plugin writes to its own log file. Tracksies HQ’s order sync logs don’t mix with Squizzie’s report generation logs or Trustie’s review submission logs.
• Toggle from the admin — No editing wp-config.php, no FTP, no SSH. Click a switch, logging starts. Click it again, logging stops and the file is cleaned up.
• Human-readable messages — Plain English descriptions, not cryptic error codes. You can often diagnose the problem yourself.
• Self-managing — Logs rotate automatically and clean themselves up. No babysitting.

Here’s what that looks like in practice:

Think of it like a flight recorder for your store. You hope you never need it, but when you do, it’s invaluable.

—

Before You Start

• Any Tracksies plugin installed and activated (Tracksies HQ, Trustie, Perkie, Packsie, Squizzie, or Pipesie)
• Admin access to your WordPress dashboard — you need to be able to see the Tracksies menu in the left sidebar

—

Per-Plugin Log Files

Every Tracksies plugin gets its own dedicated log file, stored in wp-content/uploads/tracksies-logs/ on your server:

Each file is completely independent. Enabling logging for Tracksies HQ doesn’t create entries in Trustie’s log, and vice versa. You only see what that specific plugin is doing.

—

Finding the Debug Panel

1. In your WordPress dashboard, go to Tracksies in the left sidebar
2. Click Settings
3. Click the Debug tab at the top of the settings page

You’ll see a grid of plugin cards — one for each Tracksies plugin you have installed. Each card shows:

• The plugin name with a coloured icon (blue cart for Tracksies HQ, gold star for Trustie, orange heart for Perkie, pink gift for Packsie, mulberry chart for Squizzie, green flag for Pipesie)
• A toggle switch on the right
• A status badge — either a green “Logging” badge with an animated pulse, or a grey “Disabled” badge
• The log file size when logging is enabled
• A View Log link when logging is enabled

—

Enabling Debug Logging

1. On the Debug tab (in Tracksies > Settings), find the card for the plugin you want to debug
2. Click the toggle switch on the right side of that card to turn it on
3. The status badge will change from grey “Disabled” to green “Logging” with a pulsing animation

That’s it. Logging starts immediately — there’s no delay or extra configuration needed. Behind the scenes, Tracksies creates a protected log directory and begins recording events.

—

What Each Plugin Logs

Tracksies HQ

When debug logging is enabled for HQ, it records:

• Customer sync — which customers were synced, what data was updated, and any failures (missing orders, invalid data)
• Order processing — order status changes, custom status transitions, HPOS compatibility events
• Priority rule evaluation — which rules were checked, which matched, what actions were taken
• Email sending — emails queued, sent, or failed, including recipient, email type, template used, and untracked email fallback decisions
• Tag calculations — tags earned or recalculated (commitment, tenure, value, engagement, price sensitivity)
• Shipping method detection — which shipping method was identified on each order, pickup detection results, delivery estimate resolution
• Typed notes — note creation events (customer/shipping/internal), dual storage writes (WooCommerce + Interactions), visibility assignments
• Cron jobs — scheduled tasks running (sync, cleanup, email queue processing) with timing information
• Returns processing — return requests received, status changes, refund actions
• GDPR privacy — erasure and export requests processed, records removed or anonymised

Trustie

• Review submissions — form validation, review creation, approval/moderation status
• Form rendering — which form loaded, demographic fields applied, any rendering issues
• Media uploads — photo upload attempts, file validation, image processing results
• Google Places API — API calls made, reviews fetched, rate limiting, authentication status
• Trustpilot API — connection tests (success/failure with business details), review fetching, cache hits and misses, mode detection (API vs TrustBox)
• Review request emails — scheduling, sending, secure link generation, unsubscribe handling
• Moderation actions — approve, reject, spam marking, batch operations
• GDPR privacy — review anonymisation during erasure requests, export data compilation

Packsie

• Dashboard loading — tab initialisation, data fetching, AJAX requests for orders/returns/customers
• Staff actions — packing confirmations, status changes, note additions (with note type)
• Pickup detection — local pickup auto-detect results, Ready for Pickup status transitions
• Kiosk mode — session checks, page protection, access control decisions
• Staff role checks — permission verification for dashboard actions

Perkie

• Points earning — points awarded per order, earn rate calculations, bonus triggers, multiplier application
• Points redemption — redemption attempts, discount application, minimum/maximum validation
• Tier calculations — tier qualification checks, tier promotions/demotions, tier-based multiplier lookups
• Referral tracking — referral link generation, referee identification, reward distribution to both parties
• Import processing — historical order import progress, points calculations from past orders, batch processing status
• GDPR privacy — points/transaction deletion, referral anonymisation during erasure requests

Squizzie

• Report generation — data source queries, tile calculations, comparison periods, template loading
• Google API calls — GA4 data requests, Search Console queries, Business Profile fetches, PageSpeed audits
• Chart rendering — data transformation for charts, axis calculations, colour assignments
• PDF export — DOMPDF rendering, cover page generation, header/footer injection
• Scheduled delivery — cron-based report emails, recipient lists, attachment generation

Pipesie

• Lead scoring — dimension calculations, flag assignment (red/beige/green), sweet spot matching
• Form capture — contact form submissions detected, field mapping, data extraction
• Notification triggers — which notifications fired, to whom, and why
• Flag evaluation — individual answer flags, override coaching prompts, pattern detection
• Project close-out — close-out form submissions, retrospective data, coaching feedback captured

—

Understanding Log Levels

Above the log viewer, you’ll see a colour-coded legend explaining what each level means. Every log entry is tagged with one of four levels so you can tell at a glance how serious it is:

Most of the time, you’ll want to look at Error and Warning entries first. Info entries are useful for confirming that things are working as expected. Debug entries are the deep detail — helpful when our support team needs the full picture.

—

Viewing Logs

1. On the Debug tab (in Tracksies > Settings), click View Log on the plugin card that has logging enabled
2. The log viewer opens in a dark theme with a monospace font — designed to be easy to read even with a lot of entries
3. Each entry shows a timestamp, a level icon, and the message
4. Some entries have an expandable Details section — click it to see the full JSON context data (things like order IDs, email addresses, and error codes)

The log viewer has a maximum height of 500px and scrolls if there are more entries, so it won’t take over your whole screen.

Here’s what a log entry looks like:

[2026-02-17 15:32:45] [INFO] Order #1234 synced successfully | {"order_id": 1234}

—

Action Buttons

Below the log viewer, you’ll find four buttons:

• Copy for Support (headset icon) — This is the one you’ll use most often. It copies the log contents along with your system information (WordPress version, PHP version, active plugins, and theme) into your clipboard, formatted and ready to paste into a support ticket. One click, and we have everything we need to help you.

• Refresh (sync icon) — Reloads the log entries. Useful if you’ve triggered an action (like placing a test order) and want to see the new entries without reloading the whole page.

• Copy All (copy icon) — Copies the raw log to your clipboard. Use this if you want the plain log text without the system information attached.

• Clear (trash icon) — Deletes all log entries. You’ll be asked to confirm before anything is deleted, so you won’t accidentally wipe your logs.

—

Sharing Logs with Support

When you need to share logs with our support team:

1. Click the Copy for Support button (with the headset icon) below the log viewer
2. The log contents are copied to your clipboard, along with system information that helps us diagnose the issue faster — your WordPress version, PHP version, active plugins, and theme
3. Paste into your support email or ticket

No hunting through server files, no downloading log files manually, no guessing which bit is relevant. The button grabs what we need and formats it so we can get straight to solving your problem.

—

Log File Management

You don’t need to babysit your log files. Tracksies handles the housekeeping automatically:

• Auto-rotation: When a log file reaches 5MB or entries are older than 7 days — whichever limit is hit first — the current log is backed up as a .old file and a fresh log starts. Only one backup is kept at a time, so your server doesn’t fill up with old logs.

• Cleanup when you disable: When you turn off debug logging for a plugin, the log file is deleted immediately. No orphaned files left behind taking up space.

• Protected storage: Logs are stored in wp-content/uploads/tracksies-logs/ on your server. Each plugin gets its own file (for example, woo.log for Tracksies HQ, trustie.log for Trustie). The directory is protected with an .htaccess file and an index.php file so the logs aren’t publicly accessible — visitors browsing your site can’t reach them.

—

Disabling Debug Logging

1. Go to Tracksies > Settings and click the Debug tab
2. Find the plugin card and click the toggle switch to turn it off
3. The status badge changes back to grey “Disabled”
4. The log file is deleted immediately — a clean slate for next time

—

Troubleshooting Workflow

When something isn’t working, here’s the fastest path to a diagnosis:

1. Identify the plugin — Which plugin owns the feature that’s misbehaving? Order sync issues? That’s HQ. Reviews not submitting? That’s Trustie. Report showing wrong data? That’s Squizzie.
2. Enable that plugin’s debug logging — Go to Tracksies > Settings > Debug, toggle on just that one plugin.
3. Reproduce the issue — Do the thing that’s broken. Place a test order, submit a review, generate a report.
4. Check the specific log file — Click View Log on that plugin’s card. Look for Error and Warning entries around the time you reproduced the issue.
5. Share with support if needed — Hit “Copy for Support” and paste into your ticket. We’ll have the full context in one shot.

You don’t need to enable logging for every plugin at once. Targeted logging for the relevant plugin gives you clean, focused output that’s much easier to work with.

—

How This Compares to WordPress Debug Mode

WordPress has its own WP_DEBUG and WP_DEBUG_LOG constants that you set in wp-config.php. Here’s how Tracksies debug logging differs:

You can use both side by side if you want. Tracksies debug logging doesn’t interfere with WordPress’s built-in debug mode.

—

When to Enable Logging

Turn on debug logging when:

• You’re troubleshooting a specific issue — emails not sending, order sync failing, calculations looking wrong
• Support asks you to — if we say “turn on debug mode,” this is what we mean
• You’re testing a new configuration — you’ve changed settings and want to confirm everything’s working as expected
• You’ve just connected a new integration — Google API, email service, etc. — and want to verify the data flow

—

When to Disable Logging

Turn it off when:

• Your issue is resolved — there’s no need to keep generating log files you won’t read
• You’ve finished testing — once you’re confident things are working

Logging has minimal performance impact — it writes a small amount of text to a file on your server, with no database queries or background processes involved. That said, there’s no reason to leave it running indefinitely if you’re not actively using the data.

—

Common Questions

Does logging slow down my site?
The impact is minimal. When debug is enabled, Tracksies writes a small amount of text to a file — no database queries, no calls to external services. When debug is disabled, nothing happens at all — no background processes, no disk writes. That said, there’s no reason to keep it on if you don’t need it.

Can anyone see my logs?
Logs are only visible to administrators in the Debug tab (in Tracksies > Settings). The log files on your server are stored in a protected directory with an .htaccess file that blocks public access — visitors browsing your site can’t reach them.

How far back do logs go?
Up to 7 days or 5MB, whichever limit is hit first. Older entries are automatically rotated out. If you need to capture something specific, enable logging before you trigger the action you’re investigating.

Do I need to enable logging for support to help me?
Not always, but it makes diagnosing issues much faster. If we can see exactly what happened in the logs, we can often solve the problem in one reply instead of going back and forth. If support asks for logs, this is where to find them.

Can I enable logging for multiple plugins at once?
Yes. Each plugin has its own toggle and its own log file. Enabling logging for Tracksies HQ doesn’t affect Trustie’s logs, and vice versa. Turn on whichever ones are relevant to the issue you’re investigating.

What happens to my logs when I update Tracksies?
Your log files aren’t touched during plugin updates. If logging was enabled before the update, it stays enabled after. Your existing log entries are preserved.

I have multiple Tracksies plugins. Do I need to check every log?
No. Each plugin only logs its own activity. If reviews aren’t working, check Trustie’s log. If customer sync is failing, check HQ’s log. You’ll never need to cross-reference logs between plugins for a single issue.

—

Troubleshooting

Debug tab not showing
Check that you’re logged in as an administrator. The Debug tab (in Tracksies > Settings) is only visible to users with admin-level access — shop managers and other roles won’t see it.

Logs are empty after enabling
Logs only record events as they happen — they don’t retroactively capture past activity. Perform the action you’re trying to debug (place a test order, trigger an email, run a sync), then check the logs again. Hit the Refresh button (sync icon) to reload entries without refreshing the whole page.

“Copy for Support” button not working
Some browsers or security extensions block clipboard access. Try right-clicking the log text and copying manually with Ctrl+C (or Cmd+C on Mac). If that doesn’t work either, take a screenshot of the log viewer and send that to support instead.

Log shows errors I don’t understand
That’s completely fine — you don’t need to interpret everything yourself. Use the Copy for Support button to grab the logs with your system information included, and paste it into a support ticket. The system info gives us the context we need to make sense of the entries.

Toggle won’t stay on after page reload
This usually means the settings didn’t save. Check your browser’s developer console (press F12 and look at the Console tab) for any JavaScript errors. If you see errors, try disabling other plugins temporarily to rule out conflicts, then contact support.

—

Need more help? Check our FAQ & Troubleshooting guide or contact support.