Attribution window, HTTPS domains, CDP automations and webhook with custom fields
Custom conversion attribution window, pre‑built RFM automations and HTTPS for tracking domains as new features. Webhook with custom fields and three fixes.
NEW
Custom conversion attribution window
In account settings (Marketer+ and CDP plans) you can now configure the attribution window length separately for opens and for clicks. Default values (10 days from open, 30 days from click) remain unchanged. The setting is in Account management → Settings → Global variables → Conversions.
NEW
CDP: pre‑built RFM segments and automations
Pre‑built segments and automations based on RFM analysis are now available on the CDP plan ‑ for contacts at risk of churning, most valuable customers, potentially valuable contacts and contacts suitable for discount campaigns. Segments are in CDP → Pre‑built segments. Pre‑built automations are available when creating them in Automations → New automation.
NEW
Tracking domains support HTTPS without a custom proxy
Tracking domains can now be secured with HTTPS by pointing the CNAME record to v2.spgo.io. The certificate is issued automatically and renews itself every 3 months. Existing HTTP domains are unaffected, the switch is optional. The setting is in Account management → Domains.
IMPROVEMENT
Automation webhook includes contact custom fields
The Send to webhook step in automations now includes a custom_fields object in the payload with the values of the contact's custom fields. Previously the payload did not include custom fields.
FIX
Template translation is preserved after further edits
Translated text in a template changed to garbled characters after any subsequent edit (indentation change, button link swap, product replacement). Translation text now remains intact regardless of further template edits.
FIX
Segment export includes contact preferences and correct diacritics
Segment export was missing custom preference values for contacts, even though the full list export included them. At the same time, diacritics in the export were displayed as unicode escape sequences (e.g. Ko\u010dka instead of Kočka). Both issues are fixed.
FIX
Automation with API trigger shows correct entry count
The automation overview with API trigger showed 0 entries even when contacts had actually passed through the automation. The entry count now reflects the actual state.
Stay up to date
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.