Debugging Integrations in Ultimate Spin Wheel
APIs are fragile. Connections drop and keys expire, so even a perfect setup will eventually hit an error. The difference between a minor glitch and lost leads is observability. Ultimate Spin Wheel includes an Integration Hub with Delivery Logs so you can see every sync attempt, read the exact API response, and retry the ones that failed.
Important: Third-party email-marketing integrations (Mailchimp, MailPoet, Klaviyo, ActiveCampaign, HubSpot, Zapier, Pabbly) and the Delivery Logs, Retry, and Manual Sync tools described here are part of Ultimate Spin Wheel Pro. In the free plugin the Delivery Logs panel shows a “PRO Version Required” notice, and because no external calls are made, no logs are recorded. Everything below assumes Pro is active with at least one integration enabled.
1. The Delivery Logs Panel (Pro)
This is your “black box” flight recorder for automations. To open it:
- Go to Spin Wheel → Settings → Integrations.
- Scroll to the Delivery Logs section (the “Automation Stream”).
- You will see a chronological table of every attempt the plugin made to send a lead to an outside service.
Each row shows the Service, the lead’s email and campaign, a Status badge, the raw Response text, a Timestamp, and a Retry action.
The Status Badges
- Success (green): The service accepted the data.
- Failed (red): The service rejected the data or the connection failed.
- Pending (amber): The attempt is queued and waiting to process in the background.
2. Reading the Response Column
The Response column is the most useful part of the log — it holds the message returned by the service and usually tells you exactly why an attempt failed. Common patterns and what to do:
401 Unauthorized / “API Key Invalid”
Meaning: The key is wrong. This usually happens when you regenerated a key in the service (Mailchimp, Zapier, and so on) but did not update it in the plugin. Fix: Paste the current key back into the Integrations settings and save.
400 Bad Request / “Member Exists”
Meaning: The request was rejected, often because the contact is already on the list. Fix: A “member exists” response is not a real failure — the person is already subscribed, which is what you want. You can safely ignore it.
404 Not Found / “Invalid Resource”
Meaning: The list or audience you are sending to no longer exists — often because it was deleted or renamed in the service while the plugin still references the old ID. Fix: Return to the Integrations settings and re-select the correct list.
500 Server Error / Timeout
Meaning: The remote service is down or responded too slowly. Fix: This is temporary. Wait a few minutes and retry — the plugin also retries background attempts automatically.
3. Retrying Failed Syncs (Pro)
Logging a failure is only half the job — the panel also lets you resend the data.
Single Retry
For a one-off failure (for example a random timeout), click the Retry button on that row. The plugin immediately re-sends that specific lead; if it succeeds, the status flips to Success.
Run Manual Sync (Bulk)
If a bad API key caused many failures, you do not have to click Retry on each row. After fixing the credential, click Run Manual Sync at the top of the panel. The system reprocesses the outstanding attempts in a background batch. Refresh the panel to watch the statuses update.
To empty the panel entirely, use Clear All Logs. This permanently deletes the log records (it does not affect your stored leads) and cannot be undone.
4. Debugging Zapier and Webhooks
Webhook-based automations like Zapier can fail quietly if the receiving side changes. Use the Delivery Logs to isolate where the break is:
- Log shows Failed: The plugin could not deliver to your webhook URL. Confirm the URL is correct in the integration settings, then Retry.
- Log shows Success but nothing arrives: The plugin delivered the payload, so the problem is downstream. Open Zap History in your Zapier dashboard — if the Zap triggered but a later step errored, fix it there, not in the plugin.
- Nothing in either place: Confirm the integration is enabled and that the campaign actually captured a lead (leads are stored regardless of sync status).
Frequently Asked Questions
Why is my Delivery Logs panel empty?
Logs are only created when an integration actually runs. In the free plugin the panel shows a “PRO Version Required” notice because integrations are a Pro feature. Even in Pro, if no integration is enabled — or no leads have been captured yet — there is nothing to log.
Do logs get deleted automatically?
No. There is no automatic purge schedule. Log entries stay until you remove them with the Clear All Logs button, so you can review failures at your own pace.
Can I still get the leads if a sync keeps failing?
Yes. Every captured lead is saved in your WordPress database independently of whether the integration succeeded. Open Spin Wheel → Leads and use Export CSV/Excel to download your contacts, then import them into the marketing tool manually. Lead capture and CSV/Excel export are available in the free plugin.
A row says “Failed” but the contact is on my list. Is that a bug?
Usually not. A “member exists” or duplicate response is reported as a rejection by the service but simply means the subscriber was already there. Check the Response text before assuming data was lost.
Related Documentation
- Email Marketing Integrations: Connect Mailchimp, MailPoet, and other services (Pro).
- Win Probabilities: How winners are chosen and coupons resolved.
Conclusion
Integration errors are part of running any automation, but they do not have to cost you leads. Check the Delivery Logs, read the Response column, retry what failed, and remember that your leads are always saved in WordPress and exportable to CSV/Excel. For more help, visit the wowDevs support center.