October 2026

This month rebuilds the flow canvas, adds control and visibility over delivery, lets you manage subscriptions, suppression and alerts, and adds a dark theme. It also connects TrueEngage to your ad platforms and adds Smart Links, custom dashboards, funnels and campaign lift.

A new flow canvas

The flow editor has a new canvas that is easier to read and quicker to build on.

• Search palette. Press /, select the + on a step's outlet or an edge, or drop onto the canvas to search for a step and place it.
• Keyboard connect. Join steps without a mouse.
• Notes and frames. Add a Note or a Frame to explain or group parts of a flow. They are not steps and do not count as stages.
• Patterns. Insert several steps at once, ready wired: Send with fallback (send a message, check whether it was opened within 24 hours, and send a second message if not) and Wait for event, else nudge (wait up to two days for an event, and send a reminder if it does not happen). The inserted steps are ordinary steps you can edit, and one undo removes the whole pattern.
• Problems panel. Lists what needs fixing before you publish.

Availability: Test and Live.

For more information, see Build a flow on the canvas.

Test a flow with one person: Stats, Debug and Dry run

Three new tabs on a flow show what it does.

• Stats. Live counts on every step and path of the canvas.
• Debug. Replay the path one person took through the flow, step by step.
• Dry run. Walk one person through the flow without sending anything or writing any data. Waits are skipped, and you can choose how event waits, goals and splits resolve. Each step says what would happen, and the tab shows which sending rules would stop the message.

Availability: Test and Live. Dry run needs permission to view users.

For more information, see Monitor a flow.

New flow steps and a new trigger

• Wait for a time window. Hold people until a window opens, such as 10:00 to 12:00. If the window is open, they continue at once.
• On error path. Steps that send a message or call another system can have an On error exit, so a failure sends the person down a path you choose instead of stopping them.
• Merge paths. Bring branches back together. A person who reaches it by more than one path continues once.
• Alert team. Send a short note to your alert destinations (email, Slack, Microsoft Teams or a webhook) when people reach a step. The note holds no personal data, and it is sent at most once every 15 minutes per step. The person always continues.
• Segment entered trigger. Start a flow when people join a segment. The first segment refresh after you publish only records who is already in; people who join afterwards enter the flow. People who leave a segment do not trigger a flow.

Availability: Test and Live. Flows need permission to manage flows.

For more information, see Flow steps and Choose how people enter a flow.

Delivery tracking for each sender

Each sender now has a Delivery tracking tab that shows whether delivery receipts from your vendor are reaching TrueEngage.

• Callback address. Copy the address to paste into your vendor's dashboard, with setup steps for the vendor.
• Health. See whether the sender is receiving receipts, when the last one arrived, and how many messages it sent recently.
• Enforce the token. Turn on enforcement so receipts are accepted only with the sender's token. You can reveal or rotate the token, and each reveal is recorded.
• Status on the list. A tracking chip on each sender shows its state at a glance.

Availability: Test and Live. Needs permission to manage channels to change settings.

For more information, see Providers.

Delivery controls: throttle, minimum delay and expiry

Delivery Controls gains three tabs beside frequency caps and quiet hours.

• Throttling. Set how many messages per minute a channel sends in batch campaigns.
• Minimum delay. Leave a gap between two messages to the same person on a channel. Transactional messages are exempt unless you choose otherwise.
• Expiry. Drop a message that has not been sent in time. For push, the remaining time is also passed to the push service.
• Quiet hours queue policy. Choose what happens to messages held during quiet hours: send them all, send only the newest per person, or do not send. You can set the order and the gap between released messages.
• Campaign overrides. In the campaign wizard, ignore the channel's minimum delay or set an expiry for one campaign. The campaign page shows the effective speed, delay and expiry and where each comes from.

A change applies to new sends only, not to messages already queued. A campaign's per-minute request limit is now enforced, so a live campaign that has one set will send more slowly.

Availability: Test and Live. Needs permission to manage channels.

For more information, see Set frequency caps, quiet hours and the Test allowlist and Create a campaign.

Suppression lists

The Email, SMS & RCS and WhatsApp hubs each have a Suppression tab. Suppressed addresses and numbers are never messaged on that channel.

• Browse. A masked list with filters for scope and reason, and a search for a full address.
• Add or remove one. Removing asks for confirmation and is recorded, with an extra warning for bounces and complaints.
• Import a list. Upload a CSV to suppress or unsuppress many at once. Every import starts as a dry run that shows counts, row errors and a sample, and you confirm before anything changes. Phone numbers must start with + and a country code.

Availability: Test and Live. Needs permission to manage channels.

For more information, see Channels overview.

Alerts and destinations

Alerts in the Analytics group tell your team when something goes wrong.

• Ready-made alerts. Start from a preset, such as a high campaign failure rate, sender sign-in errors, stale delivery tracking, a drop in event volume, or ingestion that has stalled.
• Destinations. Send alerts to email, Slack, Microsoft Teams or a webhook. Webhooks can be signed. Use the test option to send a test note.
• Incidents. One incident opens when an alert fires and resolves when the problem clears. A short cooldown stops repeat noise. Acknowledge an incident from its panel.
• Subscribe. Follow an alert yourself and get its notes by email. Manage your own subscriptions under Notifications in your profile.

Availability: Test and Live. Needs permission to view alerts; creating needs Create and manage.

For more information, see Console tour.

WhatsApp: General settings, Karix and Aisensy

• WhatsApp hub. WhatsApp has its own hub with Senders, Subscription categories, Suppression, Templates and General tabs.
• General. Choose the attributes that hold a person's WhatsApp number and opt-in, and set whether to keep inbound messages. These settings are saved, but they do not yet change who receives sends.
• Karix and Aisensy (beta). Connect either as a WhatsApp sender. Both are in beta, so run a Test send before you rely on them.
• Register a template by ID. Karix, Aisensy and ValueFirst have no template list to sync. Register each template with its vendor template ID instead. Templates the vendor has approved can be used in campaigns.

Availability: Test and Live. Needs permission to manage channels.

For more information, see Providers.

Subscription categories

Create categories such as Newsletter or Promotional so people can opt out of one kind of message without leaving all of them.

• Manage categories. A Subscription categories tab on the Email, SMS & RCS and WhatsApp hubs lists each category with its opt-out count. Archive one when you stop using it.
• In campaigns. Choose a category in the campaign wizard. People who opted out of it are skipped.
• In flows. Choose a category on a Message or Best channel step. The dry run shows who would be skipped.
• Opt-in categories. For an opt-in category, people with no recorded choice are not messaged.

Transactional categories are never blocked.

Availability: Test and Live. Needs permission to manage channels.

For more information, see Create a campaign and Flow steps.

Scheduled and emailed reports

Send a saved report to your team on a schedule. Select Schedule on a saved report, then pick who receives it and when.

• Schedules tab. See each schedule's status, next run in its time zone and run history. Pause a schedule or select Send now.
• Aggregate only. Emails contain totals and a CSV of aggregated figures, never people-level rows. Each recipient gets an unsubscribe link.
• Access is re-checked. A report is sent only if the schedule's owner can still see it.

Availability: Test and Live. Needs permission to manage analytics.

For more information, see Reports.

Attribution defaults

Set workspace-wide rules for how conversions are credited, under Settings > Attribution.

• Default window. Applies to goals that do not set their own, and to the ad analytics cohort window.
• Channel goal rules. Make a goal required or default for a channel.

Existing goals and campaigns are not changed. Each change is recorded.

Availability: Test and Live. Needs permission to manage settings.

For more information, see Settings overview.

UTM defaults and per-flow UTM

TrueEngage can tag the links in your messages with UTM parameters for you.

• Workspace defaults. Under Settings > UTM defaults, turn tagging on and choose the source, medium, campaign and content templates. Only links to your allowed domains are tagged.
• Campaign values. A campaign's own UTM values take precedence over the workspace defaults.
• Per flow. In a flow's Settings tab, Link tracking (UTM) overrides any of the four values for that flow. Use workspace defaults clears them. The Dry run tab shows which values would apply.

Tagging does nothing while workspace tagging is off.

Availability: Test and Live. Needs permission to manage settings.

For more information, see Flow settings and Create a campaign.

Branded tracking links

Email and SMS links can be tracked on your own link domain instead of the sender's address. Open the Tracking links tab on the Email or SMS & RCS hub and choose a verified link domain. Clicks are counted and people are redirected to the original page. Unsubscribe, preference and view links are unchanged. If the domain stops serving, messages go back to normal tracking.

Availability: Test and Live. Needs permission to manage channels and a verified link domain.

For more information, see Smart Links domains.

File segments

Build a segment from a file. On Segments, choose Upload a list, select a file and check the result before creating. The check shows how many rows match your users and which do not. The file is read in your browser, and you confirm with a check code before the segment is created. Upload again to update an existing list.

Availability: Test and Live. Needs permission to manage segments.

For more information, see Segments.

Developer page with Live events

Settings > Developer helps you check an integration.

• Live events. The last 24 hours of events received and rejected for the environment, with filters, pause and refresh. Rows show the event name, time, source, SDK version and, for rejected events, the reason. People appear only as a short hashed tag.
• API request builder. Build and copy a request for the public API.
• SDK debug guide. Steps to confirm an SDK is sending.

Availability: Test and Live. Needs permission to view API keys.

For more information, see SDK ingest.

Dark theme and Appearance

The console now has a dark theme. Choose Light, Dark or Match system under Appearance in your profile, or from the account menu. Message previews stay light so you see what recipients see. The setting is kept in your browser.

Availability: Test and Live.

For more information, see Account settings.

A redesigned account menu and profile

• Account menu. A header with your photo, name, email, role, workspace and environment, an inline Light, Dark or System switch, and links to Profile & security, Signed-in devices and Documentation. It works with the keyboard.
• Profile tabs. Your profile is split into tabs, and the address keeps the tab.
• Sessions and devices. See where you are signed in and sign out any device.
• Profile photo. Upload and crop a photo. It appears in the top bar.

Availability: Test and Live.

For more information, see Account settings.

Styled push text on Android

Push titles and messages can use bold, italic, underline and colour. Select Style text next to the title or message in the template editor. The preview shows the Android result and warns when the colour has poor contrast. Android shows the style; iOS and web show plain text. Needs Android SDK 0.9.0 or Flutter 0.9.0.

Availability: Android and Flutter (on Android). Test and Live.

For more information, see Create a template and Push notifications.

Settings hub

Settings now opens an All settings hub that groups every settings page, so the sidebar stays short. Storage & Assets sits under Settings.

Availability: Test and Live.

For more information, see Settings overview.

Ad platforms: conversions, audiences and tracking

Connect Google Ads, Meta and Google Analytics 4. TrueEngage records the ad behind each user, sends the events you choose as conversions, and keeps segments in sync as ad audiences.

• Conversions from the server. Map an event, such as a purchase, to a platform conversion. Set conditions, a value, a currency and an event ID pattern. Test it before it goes live. Events are hashed and sent about a minute after they happen, with retries for hours.
• Connect Meta two ways. Sign in with Meta for conversions and audiences, or paste a dataset ID and access token for conversions only.
• Connect Google Ads. Sign in with Google. Conversions upload with the click id, or with hashed email and phone. Audiences use Customer Match.
• Audience sync. Send a segment to Google Ads or Meta from Sync to ads on the segment or from a connection's Audiences tab. Each audience shows its status: ready, syncing, processing, too small or needs reconnect.
• Ad audience step in Flows. Add people to an audience, or remove them, at any point in a flow.
• Tracking tab on profiles. See the first and last touch, the click ids and device ids held for the user (masked, with an audited reveal), and their ad consent.
• Attribution dimensions. First and last touch values, such as campaign, media source and ad platform, work in segments and as analytics breakdowns.
• Ad tracking import. Load past touches for existing users from a CSV. See Import past ad tracking data.
• Consent first. Only users with ads_consent set to true are sent.
• Health and reconnect. Connections are checked every 6 hours. When a platform stops accepting the sign-in, mappings and audiences pause and resume on their own after you reconnect.
• Per-app Firebase app ID. Add it on an app so GA4 can attribute app events.

The SDKs 0.7.0 capture UTM values and click ids from links and installs. See SDK release notes.

Availability: Test and Live. Connecting and changing mappings needs Create and manage on Ad platforms.

For more information, see Ad platforms.

Erase a person and follow privacy requests

Delete one person's data on request, from their profile or from your backend.

• Erase person. Open a profile, select the three-dot menu, then Erase person…. Give a reason and type the workspace name to confirm. TrueEngage removes the person from ad audiences first, then deletes their profile, devices and identifiers. Event and message history stays, without personal data.
• Privacy requests. A new page under Settings lists every erasure with who asked, the reason, the stage and the due date. Open one to see progress, what is holding it up and a Reconnect link when an ad connection needs attention.
• Erasure API. POST /v1/privacy/erase and GET /v1/privacy/requests/:id, with a server key that has the GDPR Delete scope.
• Identifiers blocked for 90 days. An erased person's identifiers cannot create a new profile or events for 90 days.
• New permission. Privacy requests has View and Create and manage. Owners and Admins have both. Managers can view.
• Ad audience warnings. When an ad platform never confirms a removal, the audience shows how many people could not be removed, why, and how to fix it.

Availability: Test and Live.

For more information, see Erasing a person.

Ad identifiers are cleared when people take them back

When a person denies tracking, limits ad tracking, resets their advertising id or opts out, the SDK now tells TrueEngage to delete the stored identifier. Ad consent that is withdrawn, or a deleted profile, clears every stored ad identifier within the hour. Device-id audiences on Meta drop the old id. Needs SDK 0.8.1.

Availability: Test and Live.

For more information, see When ad identifiers are cleared.

Template editor and personalisation filters

Write personalised messages with help from the editor, and see the result as you type.

• Filters and conditions in every field. Use filters such as upper, truncate, date, map, number, currency and percent, and {{#if}} conditions, in every text field, including a push title and message.
• Arithmetic and fallbacks. add, subtract, multiply and divide calculate with a number or another variable. a || b uses the first variable that has a value. Text that is not a number passes through unchanged.
• Angular-style number formats. For example number:"1.0-2".
• Highlighting and suggestions. Template fields colour your variables, flag mistakes and suggest variables, conditions and filters as you type.
• Insert panel. Pick a variable, filter, condition or smart link instead of typing it. A wired event picker fills in that event's properties.
• Live preview. The preview evaluates your filters and conditions against a sample event. Paste a bare sample event as JSON.
• Clear save errors. A template with a syntax mistake names the field and the problem.
• Longer push text. The push title and message accept more characters.

Availability: Test and Live.

For more information, see Personalise your messages.

API-triggered campaigns, and flows that skip days

• Trigger a campaign from your server. Call the campaign's trigger endpoint with a list of users, a segment or everyone, plus template variables. Repeats within 24 hours are ignored.
• Optional audience. An API-triggered or event-triggered campaign no longer needs an audience. Event-triggered campaigns show as Live once active.
• Skip dates. Recurring campaigns and fixed-time flows can skip chosen days, read in the schedule's time zone.
• Flow recipients. Flows have a Recipients tab with delivery columns, and variables show the name of their source.
• Schedule time zones. The time zone picker on a campaign's Delivery step now opens and lists zones by name.

Availability: Test and Live.

For more information, see API-triggered campaigns.

A new look

• Geist typeface and Tabler icons. The console uses the Geist font, and a new, lighter set of icons replaces the old one.
• Sidebar. Labels are in Title Case, Apps is a top-level link, and Smart Links has its own group.
• Accent colour. The workspace accent colour setting is removed.
• One sign-in across tabs. Several browser tabs share one session, so a refresh in one tab no longer signs you out of another.
• Readable device names. Profiles and activity show Apple marketing names, such as iPhone 15, instead of model codes.
• Charts. Funnel steps, bars and dashboard tiles use the same eight-colour palette.

Availability: Test and Live.

Home page and push test sends

• Home shows what your workspace holds. Counts of users, segments, campaigns, flows, templates, providers, apps, Smart Links, data and workspace members, for the environment you are in. It does not show analytics.
• Per-recipient test results. A push test send reports each recipient: which provider carried it, every attempt, and whether a device was missing.
• Paste a device token. Test a push to a raw token. TrueEngage tries your providers in turn and says when a token cannot be routed.
• Clear notice for trial limits. A provider's trial refusal is shown as such, and never removes the device.

Availability: Test and Live.

For more information, see Console tour and Send a test.

Smart Links

Share one link that opens your app on the right screen, sends people to the store when they have no app, and still opens the right screen after they install.

• Links, templates and domains. Use a free shared name or your own subdomain. Templates set which app opens, where people without the app go, and how the link looks when shared.
• Deferred deep links. The app opens on the linked screen after an install. SDK 0.4.0 or later.
• Rules. Send clicks from some countries or platforms elsewhere, and expire a link by date or after a number of clicks.
• QR codes. Download PNG or SVG, with your logo. Scans are counted.
• Bulk create. Import links from a CSV and export the list. People are never exported.
• Link analytics. Clicks, installs and opens per link, and a Smart Links dashboard.
• Tracking. Web click ids, click webhooks, signed links and optional retargeting pixels.
• Ad click ids. A click stores the Google and Meta click ids, so the install and later conversions reach the ad. See Smart links and ad conversions.
• Referral links from the app. createLink makes a link from inside the app. SDK 0.5.0 or later.

Availability: Test and Live. Creating needs Create and manage on Smart Links.

For more information, see Smart Links overview.

Custom dashboards and dashboard templates

Build a dashboard from the tiles you care about instead of using a fixed layout. Lay tiles out in titled rows of up to six cards, and share the result with your workspace or keep it private.

• Six kinds of tile. Add built-in tiles, funnels, RFM models, reports, saved-segment cards and a count of any event.
• Your own default. Star a dashboard to make it the one you land on. The choice is yours alone.
• Compare to the previous period. Switch on a comparison for the whole dashboard.
• Safe sharing. Anyone who can view analytics can open a shared dashboard. Only its creator or the workspace owner can change or delete it. Everyone else can duplicate it.
• Dashboard templates. Install a ready-made set of funnels, RFM models and tiles by matching each step to your own events. Installing in Test leaves Live untouched.

Availability: Test and Live. Creating dashboards and installing templates needs permission to manage analytics.

For more information, see Build a custom dashboard and Install a dashboard template.

Funnels up to 20 steps

Find where people drop off in a journey of up to 20 steps, and see how different groups and different timings compare.

• Flexible steps. A step can match any of several events, and each event can be narrowed by a property, such as only Product Viewed where category is Shoes.
• Rules you choose. Set a conversion window of up to 90 days, count people in order, in strict order or in any order, and count unique people or every attempt.
• Compare to a segment. Put a saved segment next to the whole audience.
• Time to convert. See how long people take to move between steps.
• Major drops called out. The biggest losses are labelled in the chart.

Availability: Test and Live. Creating and editing funnels needs permission to manage analytics.

For more information, see Build a funnel.

Reports: Trends, Breakdown and Retention

Answer one question about your events and save the answer to reuse it or add it to a dashboard.

• Trends show how often events happen over time, with up to five series.
• Breakdown splits one event by a property or attribute as ranked bars.
• Retention shows how many people come back after their first time.
• Imported history is your call. Include events you imported from a file, or leave them out.

Availability: Test and Live.

For more information, see Build a report.

Built-in dashboards

Five dashboards need no setup: Key Metrics, Campaign Stats, Activity View, Deliverability and Reachability.

• Campaign Stats credits conversions the way you choose: messages marked converted, click-through, view-through or in-session.
• Activity View covers events, screens and technology, with a switch between all, custom and standard events.
• Deliverability and Reachability show delivery rate, impression rate and how many people you can reach on each channel, including WhatsApp.
• Drill into the people. Select a tile to see who is behind the number, with contact details masked, and save that group as a segment.
• Table view and download. Every widget can be read as a table and downloaded as a chart image or CSV.

Availability: Test and Live.

For more information, see Built-in dashboards.

RFM segments

Sort customers by how recently, how often and how much they buy, and act on each group.

• Group sizes over time. See how many customers sit in groups such as Champions and At risk.
• Movement. Compare two days to see who moved up or down.
• Act on a group. Save a group as a segment, or start a campaign for it.
• Use groups in other segments. RFM groups are available in the segment builder.

Availability: Test and Live.

For more information, see RFM results and Create and manage RFM models.

Conversion goals and campaign lift

Measure what a campaign or flow caused, not only what happened after it.

• Goals are now evaluated. Campaigns and flows credit conversions to the message that reached the user. Each conversion event is credited once.
• Lift against a control group. Hold back up to 50% of reachable users. The campaign page compares both groups and shows the incremental conversions and a confidence verdict. Flows show goal lift the same way.
• Events that count as conversions. Mark an event as a conversion once and every campaign and flow can use it.
• Credit windows from 5 minutes to 30 days.
• Replay over past events. When you change a conversion, choose whether it also applies to past events. The Conversion history tab shows each background run and lets you cancel or retry it.

Availability: Test and Live. Changing conversions needs permission to manage data.

For more information, see Campaign detail, Manage events and Conversion history.

Events and user attributes in Data management

See everything your apps, servers and imports send, and tidy it up.

• Events tab. Give events readable names, categories and a severity. Those labels appear in pickers, user activity and reports.
• Where it's used. See which segments, campaigns, flows, funnels and reports use an event.
• User attributes tab. Give attributes display names, hide them from pickers or block them.
• Hide or block. Hide a name from pickers, or block it from being stored. You can also turn on auto-block for new event names.

Availability: Test and Live. Editing needs permission to manage data.

For more information, see Data management, Manage events and Manage user attributes.

CSV imports: several files, dry runs and clearer results

Imports are now easier to check before you commit to them.

• Several files in one import. Add more files to an import and run or dry-run each file on its own.
• Dry run. Check every row and see what would be created, updated, skipped or failed. Nothing is imported until you choose Run for real.
• Know what each row did. A summary strip, running totals and a per-row outcome show what happened. A warning names columns in an added file that the mapping ignores.

Availability: Test and Live. Imports need permission to manage data.

For more information, see Import a CSV file and Import runs.

Device location and better cities

Mobile networks often place users at the carrier's head office, so a user in Bhopal can read as Navi Mumbai. TrueEngage no longer guesses a city from a carrier address.

• Opt-in device location. Your app can ask for location and send a city and region from the device. The SDK never asks unless your app does.
• Country fallback. SDKs also send the device's country, with no permission, for VPN and proxy traffic.
• Location on profiles. A user profile shows the device location when the person allowed it.
• Consent trail. Location Permission Granted and Location Permission Denied events show how many users accept the prompt.

This needs SDK 0.3.0 or later. Google Play and the App Store require your own in-app disclosure before the prompt.

Availability: Android, iOS, Flutter and Web SDKs.

For more information, see Device location and the SDK release notes.

Register your apps

Add your Android, iOS and web apps to a workspace so TrueEngage can check that events come from your app.

• One app per platform. Mobile apps verify themselves on the first event from the SDK.
• Web apps verify through DNS or a meta file.
• Push destinations. An app's registration also decides where its push messages go.

Availability: Test and Live. Needs permission to manage apps.

For more information, see Register your apps.

Find any user and read their profile

Look people up and see what they did.

• Search by any identifier. Use a mobile number, email, external id or TrueEngage id.
• Profile with activity. See identity, devices, location, lifecycle figures and a timeline of events and messages, including messages that were skipped and why.
• Masked contact details. Phone numbers and emails are masked. Revealing one needs a reason, and the reveal is recorded.

Availability: Test and Live. Needs permission to view users.

For more information, see Search for a user and User profile.

Promote from Test to Live

Build and check in Test, then copy the finished work into Live.

• Templates, segments and campaigns. Promote each one with a button on its page.
• A promoted badge. It shows what was copied and when.
• Gates. Promotion refuses items that cannot work in Live, such as a static segment.

Availability: Test to Live.

For more information, see Promote to Live.

Push platform and provider choice

Decide where a push goes and which vendor sends it.

• Platforms and devices. Pick Android, iOS and Web for a push campaign. Users with no device on those platforms are skipped, with a reason.
• Provider and sender. Leave the provider on automatic, or pin one provider per platform. For email, set the sender for a campaign.

Availability: Test and Live.

For more information, see The campaign wizard and Providers.

Campaign recipients and run status

See who got a message and why a run is still open.

• Recipients tab. A searchable list of recipients with each person's outcome.
• Held messages. A banner says how many messages are waiting, and why, when a run is waiting on delayed messages.
• Skipped and failed sends. Skip reasons show on each run, and failed sends now appear in delivery reporting.

Availability: Test and Live.

For more information, see Campaign detail.

A public docs site

The TrueEngage documentation is now available at /docs without signing in.

• User Guide. How to use the console, from setup to results.
• Developer Guide. The Android, iOS, Web and Flutter SDKs.
• API Guide. Server-side endpoints, errors and conventions.
• Release Notes. This tab. Find what changed month by month and version by version.
• Search. Press Ctrl K (Cmd K on a Mac) to search.

Availability: everyone.

For more information, see Introduction.

A tidier console

The sidebar groups pages into collapsible sections, and the console remembers which are open. RFM segments sits under Audience next to Segments. Info-severity events now show in blue.

Availability: Test and Live.

For more information, see Console tour.

Fixes and improvements

• The Segments list and detail pages count the whole population correctly, and snapshots no longer offer edit or recount.
• A segment saved from a dashboard drill-down is a snapshot, and says so.
• The SDK lifecycle events are labelled Standard, not System.
• Fixes to cropping a workspace avatar.
• Dashboard drill-downs now cover Key Metrics, Activity View, Reachability and event-count tiles, and the weekly and monthly active user cards list the people they count.
• Smart Links domains have a section menu for redirects, slug rules, branding, QR codes, tracking and webhooks.
• Merged profiles show one combined history.
• Chart labels, legends and tooltips are clearer, with an eight-colour palette.
• Signing in as another person no longer shows the previous person's name and profile.
• Signing in from a shared office network is no longer blocked by "Too many requests".
• Opening a campaign's ad sets on the Campaigns page now lists them instead of an empty table.
• The first tab's content no longer sits against the tab underline on a connection's page.
• Flows with branches, such as an A/B split, can be published again.
• Flows started from the API now run for the people you enter.
• A running flow's header shows its live version instead of "Not published yet".
• The flow entry-limit hint now describes how re-entry works.
• Idle sessions now sign out after a period of inactivity, with a warning first.
• Tracked links in messages now go only to the destination stored with the message, never to one supplied in the link.
• Campaign lists can be filtered by Running, Scheduled and Published.
• Web push devices are no longer marked as uninstalled after a browser clears its storage.