Amplitude Release Notes

WHAT IT IS

Description: You can now schedule when an experiment or flag stops, not just when it starts. Set a start time, an end time, or both. At the end time, delivery stops, the analysis window freezes, and the experiment moves to Completed (Pending decision).

What's included:

• Start and end in one modal — check Start time, End time, or both; a Runs 14 days summary confirms the window before you commit
• Auto-stop at the end time — experiments stop delivering variants, flags turn off
• Analysis window freezes at the scheduled stop, so results don't keep extending past the intended end
• Status moves to Completed (Pending decision) and the active-experiment quota slot is released for the next test
• Owners get notified when a scheduled start or stop fires
• Schedule details in the status pill tooltip — see exactly when it starts and stops

Why: Teams had to stop experiments by hand. Miss the window and variants keep shipping past the planned end — stretching analysis and holding an active-experiment slot. Time-boxed tests now end on schedule.

Where: Experiment or flag page → Start Experiment → Schedule. Once running, use Edit schedule.

Available in EUDC: Yes

When: Now!

Docs: https://amplitude.com/docs/feature-experiment/workflow/experiment-test#schedule-your-experiment

The Web Experiment script now supports cookie consent gating. Customers can defer all device storage and third-party requests until a visitor consents — while still running experiments flicker-free while consent is pending.

WHAT IT IS

Description: The Web Experiment script now supports cookie consent gating. Customers can defer all device storage and third-party requests until a visitor consents — while still running experiments flicker-free while consent is pending.

Why: EU customers (and others with CMP banners) need to run web experiments without writing cookies, localStorage, or sessionStorage — or firing impressions to third-party origins — before consent. Previously the only safe option was blocking the script entirely, which meant no experiments and visible flicker when consent arrived. This gives a compliant default that still delivers the test experience.

What’s new:

• consentOptions on window.experimentConfig — opt in with consentRequired: true
• window.webExperiment.setConsentStatus() — wire your CMP callback ('granted' / 'denied')
• Script behavior
  • While pending: experiments evaluate and variants apply with no flicker; cookie/storage writes, impression events, and the RTBT relay iframe stay in memory only
  • On grant: buffered identity, storage, and impressions flush to the device; relay loads
  • On deny: client doesn’t start (or erases prior-session data on revocation); nothing persists from the pending buffer

Available in EUDC: Yes

When: Now!

Docs: amplitude.com/docs/web-experiment/cookies-and-consent-management

Implementation snippet:

<script>
window.experimentConfig = {
  consentOptions: {
    consentRequired: true
  },
};
</script>

<!-- Web Experiment script tag -->
// CMP callback
window.webExperiment?.setConsentStatus('granted'); // or 'denied'

Notes:

• This gates Web Experiment only. Analytics consent is separate — pair with Browser SDK cookies & consent if they use both.
• Works with the anti-flicker snippet and cross-subdomain identity/RTBT.

Show a guide or survey in more than one situation without duplicating it, by adding several trigger conditions to a single one.

WHAT IT IS

What it is: Add more than one trigger condition to a single guide or survey. The conditions combine as an OR list, so the experience launches when any one of them is met. This replaces the previous workaround of duplicating a guide and giving the copy a second trigger, which meant maintaining two of everything. One behavior change worth knowing: session properties moved from the trigger level to the nudge level, so a session-property condition now gates every trigger in the set rather than a single one.

Why: Customers may want to specify multiple different conditions that should trigger their guide or survey and up until now our best recommendation has been to duplicate the guide or survey and to specify the new one with your additional trigger condition.

Where: Available on the Setup tab when configuring a web guide or survey. Mobile not yet available.

Available in EUDC: Yes

When: Now!

Ask questions about your product data from a Discord channel and get an answer back with charts, without switching over to Amplitude.

WHAT IT IS

Run '/amplitude' with a prompt in a Discord server channel to ask a question about your product data. Amplitude answers in the channel with chart images and suggested follow-up buttons, running the query as you and respecting your existing project permissions. Setup has two parts: each person connects their own Discord identity from Personal Settings, and a Discord server admin installs the Amplitude bot into the server. The agent currently uses your last-used project, or your only project if you have just one.

Where: Any Discord server channel, via /amplitude. Connect your account at Settings > Personal Settings > Connected Apps > Discord.

Who: Organizations with Global Agent enabled.

Available in EUDC: Yes

When: GA now

WHO IT'S FOR

Free

Plus

Growth

Enterprise

Must have Global Agent enabled.

DOCUMENTATION

Integrate Discord https://amplitude.com/docs/analytics/integrate-discord

RELEASE DETAILS

RELEASE ID

amplitude-global-agent-in-discord

SHIPPED

Aug 18, 2026

AREA

AI

Spend less of your agent's context on tool definitions and more on the actual question, with a smaller and more task-shaped set of MCP tools.

WHAT IT IS

The Amplitude MCP server exposes a smaller set of outcome-based tools rather than one tool per operation. An agent picks a goal, like working with dashboards or cohorts, and passes an action, instead of loading separate tools for each CRUD step.

In internal measurement of the customer-facing tool surface, the upfront tool schema payload dropped by roughly 42%. Workflows that previously took several turns also collapse: dashboards and notebooks accept temporary chart-edit IDs and promote them server-side, so query, save, and insert happen in one call. When an event or property name doesn't resolve, the error returns the closest matching real names instead of asking the agent to go look them up.

Why: Not every MCP client supports dynamic tool search and the excessive context bloat caused due to our server required more end user tokens.

Where: Nothing to configure — the tools change automatically in any MCP client connected to Amplitude. Legacy tool names stop being advertised.

When: GA now

WHO IT'S FOR

Free

Plus

Growth

Enterprise

Available on the external MCP server.

Find the event you meant on the first try, with search that accounts for what your team actually uses instead of text match alone.

WHAT IT IS

Description: Typing in the event dropdown now ranks results on more than text match. Search blends the text match with how often an event is queried across your org, how recently it has been used, and whether it's marked official in your taxonomy, so governed and commonly used events surface first. The Frequently Used list that appears before you type is now personalized to the events you pick most often, falling back to org-level usage where there isn't enough history for a given user.

Where: Event dropdowns in chart builders and related event pickers

Who: All plans. EUDC: Yes.

When: GA. Available now

Get a prioritized list of what's actually wrong with your taxonomy, each with a proposed fix you can approve or decline.

WHAT IT IS

The Data Assistant Agent reviews your taxonomy and surfaces a prioritized list of recommended fixes, drawing on how your events are used, your AI-controls context, and your project stats.

Key features include:

• New prioritized recommendations on Data Home:
• Old/stale data clean-up: Identifies broken or irrelevant events and properties for deletion or scheduled deletion to reduce clutter and prevent exceeding taxonomy limits.
• Semantic duplication: Detects semantically similar events and suggests merges or draft descriptions to clarify differences.
• Interactive agent via Global Chat / Agents: Users can ask questions, perform custom audits, diagnose issues, and act on them within a single conversation.

Why: As reliance on AI grows, trust in data quality becomes crucial. Many customers have accumulated complex data over time, requiring assistance in cleaning and managing it for effective AI adoption. The new suggestions help users identify and act on issues efficiently.

Where: Available in Data 1 Data Home (recommendations appear at the top) and via the chat icon in the bottom right. Agents can also be created in the Agents section.

Available in EUDC: Yes

When: GA now

WHO IT'S FOR

Free

Plus

Growth

Enterprise

Available to those with AI capabilities enabled

RELEASE DETAILS

RELEASE ID

data-assistant-agent

SHIPPED

Aug 13, 2026

AREA

Data

Customers in any paid tier can now upload images to change/insert images in the web experiment visual editor.

WHAT IT IS

Description:

Customers in any paid tier can now upload images to change/insert images in the web experiment visual editor.

Why:

Customers have been asking for this simple feature for a while and now they are able to upload images just like in Guides and Surveys rather than upload to their own CDN and then manually copying the link.

Where:

Visual Editor element toolbar or the 'Insert' panel (previously 'Widgets')

Available in EUDC:

Yes

RELEASE DETAILS

RELEASE ID

image-upload-in-web-experiment

SHIPPED

Aug 10, 2026

AREA

Experiment

Put a guide or survey inside your mobile app's own layout, as a card that belongs on the screen rather than an overlay on top of it.

WHAT IT IS

Customers can now embed guides and surveys inline within their mobile app UI as card embeds — anchored to a specific view rather than shown as an interrupting overlay. This brings mobile to parity with web and solves a gap where mobile guides and surveys could only appear as pop-up form factors (modals, banners, tooltips, pins), with no way to place persistent, non-intrusive content directly inside a screen.

Why: Mobile guides and surveys could only appear over the app as a modal, banner, tooltip, or pin. Anything that needed to sit in the layout was not possible: an always-visible feedback card in Settings, an NPS prompt inline after an account change, an education card living in a home feed. Card embeds existed on web, and the mobile docs said plainly that embeds weren't supported on native SDKs.

Where: Create a guide or survey and choose the Card Embed form factor. Anchor it to a target element in the app using an element identifier and configure position (before, after, or replace), alignment, and margins.

Available in EUDC: Yes

When: Available now with G&S mobile SDKs 3.12.0 or later

Useful Resources: Guides and Surveys Card Embed Form Factors Documentation

DOCUMENTATION

Card Embed Documentation https://amplitude.com/docs/guides-and-surveys/form-factors#card-embed

RELEASE DETAILS

RELEASE ID

embedded-guides-surveys-on-mobile

SHIPPED

Aug 05, 2026

AREA

Guides and Surveys

When a user opens an article from a Resource Center search result, matched search terms are now highlighted inside the article and the view automatically scrolls to the relevant passage.

WHAT IT IS

Description:

When a user opens an article from a Resource Center search result, we now highlight the matched search terms inside the article and automatically scroll to the passage the search hit came from. Previously, users landed at the top of the article and had to find the relevant section themselves.

Why:

Users searching the Resource Center are usually looking for one specific answer, not a whole article. Especially in longer docs, landing at the top means scanning and re-searching within the article — exactly the friction the search was supposed to remove. Now users go from search result to the relevant passage in one click.

When:

Available today, works with the existing SDK — no changes needed on the customer side.

The Guides and Surveys SDK now supports opening the Resource Center directly on a specific article.

WHAT IT IS

Description:

The Guides and Surveys SDK now supports opening the Resource Center directly on a specific article. Pass the article's URL to rc.open() and the widget opens straight to that content item instead of the Resource Center home page:

window.engagement.rc.open({ url: "https://help.example.com/articles/getting-started" });

Why:

Customers want to deep-link users to the right help content in context — e.g. a "Learn more" button next to a feature that opens the relevant article in the Resource Center, without the user having to search for it or leave the app. Until now, rc.open() could only open the Resource Center home page.

Available in EUDC:

Yes

When:

Available today

The Data Tables attribution model picker now includes Last Non-Direct Touch - all credit for a metric goes to the most recent touchpoint that isn't Direct.

WHAT IT IS

Description: The Data Tables attribution model picker now includes Last Non-Direct Touch - all credit for a metric goes to the most recent touchpoint that isn't Direct. You choose which property defines your channels and what counts as "Direct" for your org, and the model skips those touches when assigning credit.

Why: Last non-direct is the commonly accepted default in B2C digital analytics - and customer comparing numbers against other tools will see aligned reporting.

Where: Data Tables → metric column → attribution model selector.

EUDC: Yes

Docs: amplitude.com/docs/analytics/charts/data-tables/data-tables-attribute-credit

WHAT IT IS

Description: The Browser SDK now captures marketing attribution (UTMs, click IDs, referrer) as event properties by default, alongside the user properties it always set. The GTM template was updated with the same behavior - so GTM-based implementations get it automatically, no custom variables needed. This is fully additive: user property attribution continues working exactly as before, no new events are generated, and existing setups are untouched. Updating the SDK / template is the whole migration.

Why: User-property attribution is locked to a single model: most recent value, no expiration. Event properties remove that lock.

With attribution carried on the events themselves, you can leverage persisted properties to apply different allocation models (first, last, first/last known), set expirations like session scope (creating Session scoped properties), and change those settings anytime - retroactively, at query time, no re-instrumentation.

Where: Browser SDK version and the GTM template (released today).

EUDC: Yes - client-side, works with any server zone.

When: SDK is live; GTM new template live with event property attribution properties capturing on by default.

Docs: https://amplitude.com/docs/sdks/analytics/browser/browser-sdk-2#event-property-tracking

Turn any image in a Guide or Survey into a clickable link, so users can jump to a page, doc, or in-app destination without needing a separate button.

WHAT IT IS

What it is: Image blocks in the Guides and Surveys editor now support a link action. Set a destination in the image block settings panel and choose how it opens: router navigation to a page inside your app, the same tab, or a new tab. This had been a longstanding request. Before this, images in guides and surveys were static, so any clickable destination needed a separate button placed next to the image.

Where: Guides and Surveys editor, image block settings panel

Who: Must have the Guides and Surveys add-on.

EUDC: Yes.

When: GA. Available now.