Eshop‑rychle integration
Ecomail now supports connecting with the Eshop‑rychle platform. The integration covers order and contact synchronisation, tracking code and product feed. You can find the setup in the Integrations section.
New Eshop‑rychle integration, improvement to the API subscribe endpoint and four fixes in automations and webhooks.
Ecomail now supports connecting with the Eshop‑rychle platform. The integration covers order and contact synchronisation, tracking code and product feed. You can find the setup in the Integrations section.
The POST /lists/{id}/subscribe endpoint now returns the subscriber_data.status field in the response with a numeric value indicating the contact state (1 = subscribed, 2 = unsubscribed, 4 = hard bounce, 5 = spam complaint, 6 = unconfirmed). The field was previously missing from the response.
Automation webhooks used the GuzzleHttp/7 header and campaign webhooks used SparkPost. Both are now unified to Ecomail Webhook ‑ the same as contact change webhooks. Clients can whitelist Ecomail requests by User‑Agent.
In certain scenarios the tag was not removed even though the contact passed through the step. The issue occurred in older automations with a specific step arrangement. The Remove tag step now works correctly.
In automations using randomly selected products, some products failed to display their price or image. The issue occurred with products whose image was stored in external storage with restricted access (Access Denied). Display is now fixed.
Once in a while, we will send a summary of new features, improvements, and fixes to your inbox. No spam, no marketing – just product updates from Ecomail.