MCP server, campaign API and segmentation fixes

Your Ecomail account can now be connected directly to AI applications that support the MCP (Model Context Protocol) ‑ for example Claude, Cursor or ChatGPT Pro. Once connected, the AI assistant can read data from your account and answer questions like 'Which campaign earned the most last month?' or prepare a new email based on results from previous sends. Access is managed via OAuth. The MCP server is available free of charge on all plans.

Enhanced conversion reports are now available on the CDP plan. You can now view conversions from selected campaigns, automations or their combination for a marketing campaign. Custom date range filtering is also available.

The IdoSell platform integration has been expanded with new data synchronisation options. Details are available in the integration settings.

A single contact tag is now limited to 50 characters. The limit is enforced everywhere a tag can be entered ‑ in the contact profile, during import and in the Add tag automation step. The API returns a descriptive error when the limit is exceeded.

The GET /campaigns endpoint now returns standard pagination parameters (next_page_url, per_page) and supports filtering by date_from / date_to and campaign ID. Filtering by ID and date range is now documented in the API reference.

Queries for A/B campaign segmentation conditions (e.g. 'Opened email but did not click') sometimes took a very long time. After query optimisation, evaluation now completes in seconds.

The condition failed to find contacts when the preference group name contained a mix of different quote types. The search now works regardless of the characters used in the group name.

When filtering contacts by a custom date field, a contact with a value exactly matching the lower boundary of the range was not found. Ranges now include both boundary values.