Contact support

Contact Searcherries at [email protected] for help with your account, projects, reports, integrations, or subscription. You can also open Support in the application and copy the email address from Contact us.

Report a problem

Include enough detail to identify the affected workflow:

• The email address of your Searcherries account.
• The project name and project-page URL, if relevant.
• The page or feature involved.
• What you expected and what happened instead.
• The exact error message and approximate time.
• The selected reporting period and data source, if the problem concerns report numbers.

For a missing Google or Bing site, mention which provider you were connecting and whether authorization or site selection failed. For Wizard, include the affected session URL rather than repeatedly submitting the same question.

A screenshot can help explain a display problem, but remove API keys, access tokens, payment details, and unrelated private information first.

Ask about a subscription

Open Subscription before contacting support. It shows your current plan, both balances, and available trial or cancellation information.

Use Manage subscription for the Paddle billing portal. If you need help with a payment, include the relevant receipt or transaction reference when available, not full card details.

The subscription guide explains plan switching and cancellation.

Suggest a feature

Describe the task you are trying to complete, how you do it today, and what would make the result more useful. A concrete example is more helpful than a feature name alone.

Questions about data

Searcherries uses connected data to provide your reports and analysis. The current Privacy Policy and Terms of Service describe the applicable terms; contact support if you need clarification for your account.

Deleting a project removes its Searcherries project data. Disconnecting an integration stops its use by that project and does not delete the original website or analytics property.

For common issues you can check immediately, see Troubleshooting.