Spin Wheel

⌘K
  2. Home
  4. Docs
  6. Spin Wheel
  8. Integrations
  10. Integration Logs: The Source of Truth

Integration Logs: The Source of Truth

“Did it send?”

This is the question that keeps marketers awake at night. You are running a campaign. People are spinning. But are they appearing in Mailchimp?

The Integration Logs feature is your answer. It is a transparent, real-time ledger of every single data transmission attempt made by the plugin. It removes the guesswork from API Debugging.

1. Locating the Logs

Accessing the logs is simple:

  1. Navigate to Spin Wheel > Settings.
  2. Click on the Integrations tab.
  3. Scroll to the bottom section labeled “Delivery Logs”.
  4. Alternatively, check the “Tools” or “Status” submenu depending on your permission level.

2. Anatomy of a Log Entry

The log table contains 5 key columns. Understanding them is the key to solving problems.

A. Date & Time

  • Format: Your local server time.
  • Use Case: Correlate this with a user complaint. “I spun at 2 PM.” Check the logs at 2 PM.

B. Service (Destination)

  • Values: Mailchimp, MailPoet, Zapier, Webhook.
  • Note: If you have multiple integrations active, you will see multiple rows for the same user (one for each service).

C. Lead (Identifier)

  • Value: The email address of the user.
  • Privacy: If “Anonymize Data” is on, this might be masked (j***@gmail.com), but usually, it is visible for debugging.

D. Status (The Verdict)

  • 🟢 Success (200-299): The receiving server said “OK.” The data is there.
  • 🔴 Failed (400-500): The receiving server rejected us.
  • 🟡 Pending: The plugin is waiting for a background worker to process this.

E. Response (The Clue)

This is the raw message from the API.

  • “Member Exists” – Good.
  • “Invalid API Key” – Bad. Fix your settings.
  • “Timeout” – Temporary network issue.
  • “Schema Mismatch” – (Zapier) You changed your webhook structure but didn’t update the plugin.

3. The “Retry” Workflow

The logs aren’t just for reading; they are for action.

Scenario: The Intern Deleted the API Key

  1. You realize at 5 PM that the API key was invalid all day.
  2. You check the logs. You see 50 rows of 🔴 Failed with “Unauthorized”.
  3. You generate a new API key and save it in settings.
  4. The Fix: You simply click the “Run Manual Sync” button.
  5. The Magic: The plugin re-loops through those 50 failed rows and re-sends them with the new key.
  6. The Result: 50 Green rows. Disaster averted.

4. Maintenance & Performance

Logs take up database space. We don’t keep them forever.

  • Retention Policy:
    • Success Logs: Kept for 30 days. We assume if you haven’t looked at it in a month, you don’t care.
    • Failed Logs: Kept for 90 days. We give you extra time to notice and fix errors.
  • Manual Cleanup: You can click “Clear All Logs” to empty the table instantly if you want to save space.

5. Frequently Asked Questions (FAQ)

Q: I see “Success” but the email isn’t in Mailchimp? 

A: Check if your Mailchimp list has “Double Opt-in” enabled. The plugin successfully told Mailchimp to add them, but Mailchimp is holding them in a “Pending Confirmation” state until the user clicks the link in their inbox.

Q: Can I search the logs? 

A: Yes. use the search box at the top right of the table to search for a specific email address (e.g., [email protected]) to trace their journey.

Q: Do Zapier logs show the payload? 

A: Due to security, we do not display the full JSON payload in the table, but the “Response” column often contains the Zapier request_id which you can cross-reference with Zapier support.

Conclusion

The Integration Log is your insurance policy. It proves that the system is working, helping you differentiate between a plugin bug, a user error, or an API service outing.

Need Help?

Logs showing cryptic errors? 👉 Contact Our Support Team

How can we help?