Eventbrite support chat is now accessible from Sync Settings, Mappings, Maintenance, and User Security, with the Support button redesigned to open a welcome panel that presents guides, contact options, and AI chat instead of jumping directly into the iframe. The overlay no longer covers the settings page with a white sheet, and the welcome panel now uses the Eventbrite e logo for branding.

The Connect page shell is restyled to Beaufort 12 white with navy and ice-blue accents, replacing the previous dark purple gradient. Overlapping steel-blue circles now echo the homepage illustration motif. The modal backdrop is softened and the card features a steel-blue accent bar for a cohesive look.

A new support welcome panel now opens from the Support launcher on the CM Subscriber Lists home, offering options to Search or chat with AI, access support guides, or contact support, and it loads the chat inside the panel. The Support launcher is now available on the CM Subscriber Lists home page. Additionally, the Help link and separator dots in the Subscriber Memberships card footer are now aligned on the same line as the Open Rate and Click Rate labels.

The in-app support widget has been redesigned to replace the old chat bubble with a dedicated Support launcher and a welcome panel. Users can access search or chat, support guides, and contact links from the new launcher. The AI chat iframe now loads only after the user starts a conversation, and new support icon assets are included to complete the refreshed experience.

Mailchimp Maintenance now records an audit log whenever an advanced setting is changed, including manual changes and automatic reductions of batch sizes. Each audit entry captures the setting name, old value, new value, who changed it, and the timestamp, with a short reason for automatic changes (Heap Limit or CPU Limit). The scope covers batch-size related settings visible in Maintenance > Advanced Settings, while non-batch settings like email notifications and the chatbot toggle remain outside the audit scope.

This release enables mapping of Salesforce STRING and TEXTAREA fields to the Mailchimp birthday merge field for the SF to MC direction, with support in both the Mappings UI and Data Wizard Map. String birthday values are validated in a locale-aware MM/DD or DD/MM format, and single-digit components are zero-padded. Invalid values are skipped for just that merge field, and a clear error is logged to Mailchimp_Log__c and surfaced to the user in the UI, without affecting the rest of the record. Existing Date and Datetime birthday mappings remain unchanged. Empty values are skipped without error.

This update closes the three certification gaps required for Xero App Store readiness: Sign Up with Xero, disconnect revocation of the Xero connection, and branded connect and disconnect buttons. Sign Up with Xero is implemented to align with Xero's partner guidelines, disconnect now revokes the Xero connection so the org is properly marked as disconnected, and the official Xero buttons ensure branding consistency. Core functionality remains unchanged.

A new totalExcluded metric has been added to McProcess.ProcessResult and is incremented at each continue during the report batch and within the filterArchivedMembers path. The results UI now displays an additional line for the number of excluded records, with an optional breakdown by reason such as invalid or empty email, in-batch duplicates, archived, and unsubscribed. Existing Created, Updated, and Errored counters remain unchanged, and the new excluded count is surfaced to improve reconciliation without altering what gets synced; note that cross-chunk duplicates and Cleaned handling remain known gaps to address in future work.

InvocableVariable descriptions and labels will now drive the MCP and Agentforce tool schemas, enabling the agent to pass the correct inputs and interpret results more accurately. The update adds labels and descriptions on every InvocableVariable in the mailchimp-agentforce McAgent_Request and McAgent_Result classes, and includes McAgentMemberAction for consistency; after deployment, you should see the new descriptions reflected in the tools and Hosted MCP schemas.

The email field selector for Mailchimp lists now consistently shows the standard Email field first, regardless of how fields are renamed. This change centralises the sorting logic so downstream components receive a pre-sorted list, improving predictability for users. A test is added to ensure the standard Email field remains first and that other fields remain alphabetically ordered.

Search and action buttons on subscriber list tables have moved from a grouped button layout to a flex span with a 0.5rem gap, ensuring each control is distinct. This update affects the SubscriberListMembers (Search and Filter) and the SubscriberListTable (Search and Refresh). To verify, open a Campaign Monitor subscriber list and confirm the toolbar shows separate buttons with a small gap, and that Search, Filter, and Refresh continue to function as before.

Emma Home now shows a Mailchimp-style setup empty state when no Emma account is connected, replacing the blocking prompt. Learn More is available for all users, while Manage Settings is restricted to users with the Emma_Admin custom permission to prevent standard users from accessing restricted tabs. Manage Settings navigates to Emma Settings / Sync Settings (em4sf__cmpId=1).

The Emma integration for Salesforce will be upgraded from API version 60.0 to 64.0, updating the project configuration accordingly. Metadata for Apex classes, triggers, Aura components, and Lightning web components will have their apiVersion set to 64.0 or higher where applicable, and any deprecated behaviour between API versions 60 and 64 will be reviewed and addressed. Packaged Apex test coverage will be verified to meet or exceed 75%, and the release will follow the standard production deployment process.

The Eventbrite Events component now supports sorting by start date in ascending order, so upcoming events are displayed chronologically. Users can view basic contact information (name, phone) along with the event date and any custom questions in a single view or report. This improvement addresses the previous behaviour where the most recent events appeared at the back of the list, making it easier to access and plan around upcoming events.

Search input and button on Emma Members and Group Members now share a single baseline by introducing a hidden placeholder label and a flexible row that enforces a 32px height for both controls, aligning with the approach used on Eventbrite lists and Campaign Monitor Subscriber Lists. The update applies to Members, Group Members, and the Email Audit modal so Search Members, Search, and Validate sit on consistent baselines across views. The changes are implemented in force-app/main/default/aura/EmmaAccountMembers and force-app/main/default/aura/EmmaGroupMembers.

The Sync Settings welcome and trailhead modals have been redesigned to replace the old SLDS welcome-mat with an editorial layout branded for Emma, aligned with the new Mailchimp-style modals. Welcome modal now features a split copy and visual panel with an Emma cyan call-to-action and a circular logo badge, while the trailhead modal presents numbered steps, a progress bar, and an ice-blue intro panel. Both cards resize to their content to avoid full-height shadows in the container, and the UX suite's dismissTrailhead now targets the .em-trail class instead of .slds-welcome-mat.

This update adds support for generating Email activity records for multivariate (A/B) campaigns within the Salesforce integration. Variants created in multivariate tests now produce corresponding activity entries, aligning recorded activity with campaign data in the UI. The change ensures subject and variant information is correctly associated with each email activity for accurate reporting of test results.

Search input and action buttons on Campaign Monitor list cards now share a single, equal-height row for Members, Campaigns, and Transactional views, matching the alignment used for Subscriber Lists and Eventbrite. A hidden label with a placeholder keeps the input on the same baseline as the buttons, and the controls render in a flex row with a 32px height for consistency. Updated components include SubscriberListMembers, CampaignList, and SmartEmailList.

After a sync marks subscriber lists as Deleted or restores them, the Subscriber Lists table could display stale rows until a full browser refresh. A Refresh button now sits next to Search on the Subscriber Lists card to re-query the table in place, and the search input and controls are aligned on a single, equal-height row. The update enables in-place refreshing and keeps the layout consistent, and you can verify by opening CM Subscriber Lists, ensuring the search and Refresh are on one line at the same height, clicking Refresh to reload the table without a page refresh, and confirming that a once-deleted row disappears after a sync.

Emma for Salesforce now uses a single, source-of-truth trial countdown based on PackageLicense.ExpirationDate, replacing prior soft-trial logic with a two-phase display that becomes urgent in the last seven days. There is no expired state shown in-app; if a licence ends, Salesforce removes the app, so in-app messaging avoids confusion. It appears in both the main licence banner and a compact countdown strip on record pages, using a consistent design language for clear visibility.

Emma for Salesforce now uses a single, source-of-truth trial countdown based on PackageLicense.ExpirationDate, replacing prior soft-trial logic with a two-phase display that becomes urgent in the last seven days. There is no expired state shown in-app; if a licence ends, Salesforce removes the app, so in-app messaging avoids confusion. It appears in both the main licence banner and a compact countdown strip on record pages, using a consistent design language for clear visibility.

Mailchimp validation errors returned by invocable actions are now persisted to the Maintenance Log, providing a durable record for review. Where possible, related Mailchimp_Member__c records will be stamped with the most recent error to aid audits and troubleshooting in later Flow steps. This enhancement preserves existing UI error behaviour and callout retry logic while introducing bulk-friendly error logging to minimise performance impact.

This update enforces that Create Only is non-interactive for any mapping row with no Salesforce field mapped, across Lead, Contact, Person Account, Campaign, Opportunity, and related screens. When a Salesforce field is selected, Create Only becomes enabled, and clearing a mapped field resets it to false and disables it again. These changes apply consistently across all mapping-row UX, reducing confusion and preserving existing runtime behaviour for mapped fields.

AnswersBatch now passes DuplicateRuleHeader.AllowSave = true when updating existing Contacts and Leads during Eventbrite answer synchronisation, aligning with the RuleBatch path. Previously, AnswersBatch used Database.update without AllowSave, which could trigger duplicate-rule blocks even though RuleBatch had already created or linked those records via DMLQueue with AllowSave=true. Eventbrite_Answer__c updates in this batch remain unchanged unless we decide they should receive the same treatment, and Mapping validation tests remain unchanged as they intentionally use plain inserts to surface duplicates in the validation UI.

During a full event refresh, the progress indicator could display as finished while AnswersBatch was still running, causing users to review Lead or Contact fields prematurely. This release ensures the progress state remains active until AnswersBatch completes for the entire sync path, including any downstream batches. An optional label such as 'Syncing custom answers' may appear while AnswersBatch is running, and batch weight percentages are adjusted to keep progress totals coherent.

The new Eventbrite Attendee Component provides a contact-level view of events attended, with attendee, order, answers, and email data accessible in a detail panel and quick-access dropdowns. This release resolves a critical issue where refreshing table-level attendee records could trigger a Primary Sync failure; refreshes will no longer produce errors and the sync continues on schedule. A small display refinement improves readability by adding space between the component title and the records count.

Email tracking history being enabled or changed now triggers a full refresh to ensure data completeness, addressing gaps from forward-looking incremental syncing. If a full refresh of tracking history isn’t feasible, the refresh will cover all tracking data to preserve accuracy. We’re also considering exposing this refresh as an option from the Sync Now button for on-demand updates.

Previously, invocable actions required an email on the triggering object. You can now pass an email field from any related or child object in the flow, enabling subscription or tag management based on records like program enrollments or opportunities even when the source object has no email. This expands flexibility for flow-driven automation, aligning with Data Wizard capabilities and common customer use cases.

This update prevents the editor from overwriting a manually set recordId when admins provide a value and resolves a save validation error for flows triggered on non-person objects. It also exposes recordId as a visible input in the Flow Builder, enabling admins to bind it to a Flow resource such as a looked-up Contact ID. Additionally, Tags and Advanced sections are now shown consistently regardless of the triggering object, with clearer guidance on how recordId is used.

This release adds CMBatchDeleteSubscribers to the allBatches synchronisation check so the primary Salesforce sync waits for delete operations started by the REFRESH AND REPLACE import to complete. This prevents race conditions and helps ensure data consistency between Campaign Monitor and Salesforce.

Mailchimp Limited now enforces read-only access for core customer-facing objects, reinforcing least privilege at both the data and UI layers. Previously only Mailchimp_Account__c was read-only, making Limited similar to Standard at the object-permission level. While the UI already hides write actions through the Mailchimp_Manage_Memberships permission, the updated object permissions prevent modifications via API, Data Loader, or custom code, enhancing overall data safety.

An enhanced workflow for the Sent and Unsubscribed activity sync now performs incremental cleanup during the synchronisation process, instead of creating all records and deleting them at the end. This reduces temporary storage usage and speeds up processing for large lists, while preserving your configured retention window. Improved error handling ensures partial failures won't leave lingering records and allows the cleanup to resume automatically.

Updates preserve existing Mailchimp Batch Size custom settings when editing mcMaintenanceSettings, preventing overwrites of user added settings and potential data loss. The release introduces a user interface option to not cap repeat Email Activity, which would raise all batch sizes to 1000 for greater throughput. It also ensures that the counts of opens and clicks in Salesforce align with Mailchimp, providing a consistent cross platform view.

Previously, enabling activity, extending the retention days, or running a full refresh would download the entire Sent/Unsubscribe activity set and delete it only at the end, potentially causing storage spikes and incomplete cleanup after errors. The update optimises the flow by performing deletions during processing in batches and improving error recovery, reducing storage usage and improving reliability for large lists. It also aims to refine how the sync keeps only the relevant records, speeding up subsequent runs.

Emails can now be filtered by archive status within Data Wizard, giving you control over which messages are included in analysis and exports. This optional filter helps you focus on active and relevant communications, improving efficiency and data accuracy.

Maintenance settings now support boolean values, enabling clear on/off configurations. A numeric slider is introduced to input values more accurately and minimise entry mistakes.

The integration now shows a clear message whenever it detects execution in a Salesforce sandbox, helping users confirm the environment and avoid confusion.

The Preview Mapping Rules modal now displays the default values, giving you clear visibility into the current configuration before you apply changes. This helps validate mappings more efficiently and reduces guesswork when reviewing setup. This enhancement applies to the Salesforce integration, streamlining the mapping workflow.

The Manage List button is now consistently enabled across all member components, eliminating instances where it appeared greyed out. This improvement streamlines workflows for managing lists within the Salesforce integration.

This release enhances the Eventbrite to Salesforce Opportunities sync by addressing contact linking, refunds, field availability for syncing, and incorrect net sales calculations. The changes include clarifying how Primary Contact population works and what conditions can prevent relationships from being established, introducing configuration options to prevent contact linking issues, and identifying which Salesforce fields reflect refunded or deleted orders to drive Salesforce Flow triggers. The update also resolves the issue where the Eventbrite Status field was not updated during sync, and makes the Eventbrite Has Contact List and Eventbrite Opted In fields available for syncing. Additionally, the Net Sales calculation is corrected to reflect ticket price minus discounts. Finally, the absence of a Closed Lost Reason has been addressed to prevent sync failures when moving Opportunities to Closed Lost.

A new dynamic capability has been introduced for the company field mapping in the Salesforce integration with Eventbrite. Eventbrite's canned fields no longer include the company name and it is now captured as a custom question. You can use pattern or merge fields in the Default Value for the company mapping to derive the name from incoming Eventbrite data, for example [FirstName] [LastName] or [EventName] [LastName]. This feature preserves backward-compatible behaviour by continuing to map the old field via Field Mappings. If needed, there are considerations for how this should apply during Account creation for Contacts, and a separate ticket will determine the best approach in that context.