Improving Outlook Performance in Outlook Non-365

Some Outlook Non-365 users may notice slower performance after installing ContactMonkey. We prioritize performance optimization and have several solutions to resolve this issue.

Solution 1: Manage Your Outlook Add-Ins

Too many active Add-ins can consume system resources and slow down Outlook. To review and disable unused Add-ins:

1. In Outlook, click File above the ribbon
2. Click Options
3. Click Add-Ins in the left sidebar
4. At the bottom of the window, locate the Manage dropdown menu and select COM Add-ins
5. Click Go
6. Uncheck any Add-ins you're not actively using
7. Click OK to save your changes

Solution 2: Send Diagnostic Logs to Our Team

ContactMonkey includes diagnostic tools that help our team identify performance conflicts. If you're still experiencing slowdowns after managing your add-ins, send us your error logs:

1. In Outlook, click the ContactMonkey tab above the ribbon
2. Click Send Log Files
3. Click Yes when the Send Log Files? dialog box appears
4. Include a brief summary of the issue you're experiencing before sending your email

Our team will analyze the logs and contact you with a resolution.

Solution 3: Check Your Antivirus Settings

Antivirus software can interfere with ContactMonkey's tracking functionality and cause delays when sending emails. Here's why:

Antivirus programs typically scan all outbound emails before they're sent. ContactMonkey injects a small tracking image into your emails, which some antivirus software may flag as suspicious and remove. This scanning and removal process can slow down email sending and prevent tracking from working correctly.

To resolve this:

Whitelist the ContactMonkey executable file in your antivirus software:

• Add cmconnect.exe to your antivirus whitelist/exception list

This tells your antivirus that ContactMonkey is safe and prevents it from interfering with tracking.

Alternative option: Temporarily disable your antivirus Add-in in Outlook to test if this resolves the performance issue. If performance improves, whitelisting cmconnect.exe is the recommended permanent solution.