> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/changelog/2024.md). # 2024 {% updates format="full" %} {% update date="2024-09-01" tags="notice" %} ## Billing system update — effective October 1, 2024 Starting October 1, 2024, eMarketeer moves to a new billing system. Key changes: * New invoice design. * **User licenses** — accounts are assigned a defined number of user licenses, visible on the User Administration page. * **Monthly prepaid billing** — subscriptions billed in advance. Two invoices issued in October during the transition; the second has a 60-day payment window. Contact with any questions. {% endupdate %} {% update date="2024-07-31" tags="feature,fix" %} ## SuperOffice signals, Delete lead step, and Excel export * **SuperOffice alarm flag** — notification bell enabled on activities created by eMarketeer. * **SuperOffice "new contact created" signal** — new contacts created in SuperOffice are automatically created in eMarketeer and can trigger journeys. * **Journey: Delete lead step** — removes a contact from all lead boards when reached. * **Export direct to Excel** — contact exports now include a direct Excel file option. * **Contact lists show name in UI** — the list name is now visible when viewing a contact list.
Fixed * Stabilised SMS sending. * Small improvements to the Dynamics 365 integration. * Fixed a bug when copying certain components in a campaign. * Fixed a bug in forms where hidden required questions prevented submission.
{% endupdate %} {% update date="2024-07-04" tags="feature,fix" %} ## Journey improvements, Lead Board filters, and API additions * Journey starting point: new date-based filters, e.g. "Last email sent". * Journeys: personalise step descriptions with contact card fields. * Journeys: view step settings on active journeys (editing disabled while active). * Lead Board: filter per sales user; filter on unassigned leads. * Application language now set under Settings → My Account. * Contact engagement filter: added 6-month range option. * API: list contact lists; delete contact. * SuperOffice side panel: show active subscriptions. * SuperOffice and Microsoft Dynamics consent sync now run on a 30-minute schedule.
Fixed * Unable to remove leads from the lead board. * Automation "Push to URL" returned success even when it failed. * Journey step "Add subscription" sometimes failed. * Unsubscribe page displayed poorly on mobile. * "Tell a friend" in emails did not always work. * Generating leads on the lead board sometimes took too long. * SuperOffice side panel social icons were missing. * Read-on-web link did not work when email content contained campaign fields.
{% endupdate %} {% update date="2024-04-18" tags="improvement" %} ## Email deliverability improvements and Dynamics CRM integration * Email domains via-em.com removed for new customers using a custom domain. * Default sending settings now require positive consent (most GDPR-friendly method). Affects new customers only. * Improved pre-sendout email validation to reduce bounces. * Email service redundancy implemented. * New contact email status: "Inactive email", with a new "Exclude inactive contacts" sendout option. * Microsoft Dynamics CRM integration phase one: connect, import from CRM, and consent sync. {% endupdate %} {% update date="2024-03-23" tags="fix" %} ## Maintenance release * Upgrade PHP and rewrite of several functions. * Rewrite of the SMS sending module for performance and stability. * Other small fixes and adjustments. {% endupdate %} {% update date="2024-02-12" tags="feature" %} ## Journeys, DMARC compliance, and SuperOffice side panel ### Journeys * **Trigger journey from contact card**, lead card, and SuperOffice side panel. * **DMARC compliance** — the "Authenticate email domain" settings page now checks all DNS records required by Google and Yahoo's email requirements. * **Manual starting point** — create journeys triggered only from the contact card. * **Step conditions** — skip steps when conditions are not met, without creating a new branch. * **Dynamic recipient on Notifier step** — use the @ character to insert contact card fields as the recipient address. ### SuperOffice side panel * **Create contact** — create a missing contact in eMarketeer directly from the side panel. * **Side panel requires no paid user** — users only needing side panel access can be created as free users. {% endupdate %} {% update date="2024-01-15" tags="feature" %} ## Journey Templates, Wait for Trigger, and SuperOffice Sale Closed signal * **Journey Templates** — choose from categorised, pre-built journeys to adapt to your needs. * **Journey step: Wait for trigger** — pauses a contact in a journey until they perform a defined action. * **SuperOffice Signals: Sale Closed** — when a sale is closed in SuperOffice, the data is sent to eMarketeer to move a lead, send a welcome email, or trigger any journey. {% endupdate %} {% update date="2024-01-01" tags="notice" %} ## Action required: Google and Yahoo email requirements (February 2024) Google and Yahoo introduced stricter email sender requirements in February 2024. If you send from a custom domain, two DNS entries are required to stay compliant. Add the following records for your domain (replace `yourdomain.com`): ``` feedback.yourdomain.com MX 10 feedback-smtp.eu-west-1.amazonses.com feedback.yourdomain.com TXT "v=spf1 include:amazonses.com ~all" ``` If you send from the default via-em.com domain, no action is needed. See [How to authenticate your domain](/getting-started/account-setup/authorize-email-domain.md) for full instructions. {% endupdate %} {% endupdates %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://support.emarketeer.com/changelog/2024.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.