Integration Logs: The Source of Truth

Integration Logs: The Source of Truth

“Did it send?” is the question that keeps marketers awake at night. People are spinning your wheel and submitting their details, but are those leads actually arriving in Mailchimp, MailPoet, or Zapier? The Delivery Logs (also called the Integration Hub) answer that question with a real-time record of every delivery attempt the plugin makes to a connected service, so you can stop guessing and start debugging.

Please note: Delivery Logs and all third-party integrations are a Pro feature (Pro). In the free plugin, opening this section shows a “PRO Version Required” panel. The log stream, manual sync, per-row retry, and log clearing all require Ultimate Spin Wheel Pro, because the marketing integrations they monitor (Mailchimp, MailPoet, Klaviyo, ActiveCampaign, HubSpot, Zapier, Pabbly) are themselves Pro.

Where to Find the Logs

1. Go to Spin Wheel > Settings.
2. Open the Integrations tab (titled “Automation & Integrations”).
3. Scroll to the Delivery Logs section at the bottom of that tab. Its “Automation Stream” table lists every delivery record.

Anatomy of a Log Entry

The log table has six columns. Understanding them is the key to solving delivery problems:

• Service: The destination the lead was sent to, such as Mailchimp, MailPoet, Zapier, or another connected service. If several integrations are active, the same lead can appear in multiple rows — one per service.
• Lead Intelligence: The lead’s email address, with the originating Campaign # shown beneath it so you can trace which wheel produced the entry.
• Status: The outcome of the attempt — Success, Failed, or Pending (see below).
• Response: The raw message returned by the service (for example “Member Exists”, “Invalid API Key”, or a timeout notice). This is your clue for what went wrong.
• Timestamp: When the attempt was made, shown in your local time. Correlate this with a user complaint to trace their exact journey.
• Actions: A Retry button that re-sends that single record to its service.

Reading the Status Column

• Success: The receiving service accepted the data. The lead is there.
• Failed: The service rejected the request. Check the Response column — an “Invalid API Key” or “Unauthorized” message means you should fix your credentials in the Integrations tab and retry.
• Pending: The delivery is queued and waiting for the background worker to process it. Integrations run asynchronously, so a lead may briefly show as Pending before it flips to Success or Failed.

Retrying Failed Deliveries (Pro)

The logs are for action, not just reading. Integrations are processed in the background, and if a service is temporarily down the system retries automatically. When the cause is on your side — for example an API key that was wrong all day — you have two manual options:

• Retry (single row): Click the Retry button on any individual record to re-send just that lead to its service.
• Run Manual Sync (bulk): The Run Manual Sync button at the top of the stream re-processes outstanding records in the background and reports how many were queued. After you save a corrected API key, one click re-sends the backlog with the new credentials.

Example workflow: You discover at 5 PM that an API key was invalid all day and the stream is full of Failed rows reading “Unauthorized”. Generate a new key, save it in the Integrations tab, then click Run Manual Sync. The plugin re-sends the outstanding records with the corrected key — disaster averted.

Clearing the Logs (Pro)

To empty the log table — for example to save space or start a clean test — click Clear All Logs. You will be asked to confirm, because this action cannot be undone. It clears the delivery records without deleting your captured leads.

Frequently Asked Questions

The status says “Success” but the contact isn’t in Mailchimp — why?

Check whether your Mailchimp audience has double opt-in enabled. A Success means Mailchimp accepted the request, but with double opt-in the contact stays in a “Pending Confirmation” state until they click the link in their inbox. This is Mailchimp’s behaviour, not a plugin error.

Why do I see multiple rows for the same person?

Each active integration gets its own delivery attempt, so a lead sent to two services produces two rows. This lets you see, per service, exactly which one succeeded and which one failed.

Does the log show the full payload sent to Zapier?

No. The table shows the raw response message returned by the service in the Response column, not the outgoing JSON body. Use that message, plus the campaign number and timestamp, to trace a specific delivery.

Why is everything greyed out with a “PRO Version Required” panel?

Delivery Logs, manual sync, retry, and the integrations they monitor are all Pro features. Upgrade to Ultimate Spin Wheel Pro to connect services like Mailchimp, MailPoet, and Zapier and to see their delivery stream.

Related Documentation

• Email Marketing Integrations: Connect Mailchimp, MailPoet, and other services whose deliveries appear in these logs.
• Lead Dashboard: Review, filter, and export the leads that feed your integrations.

Conclusion

The Delivery Logs are your insurance policy: they prove whether each lead reached its destination and help you tell a credential mistake apart from a service outage. Watch for Failed rows, fix the underlying setting, and use Retry or Run Manual Sync to recover the backlog. Remember that this Pro feature runs alongside Pro integrations — if you need help, visit the wowDevs support center.