Announcements

Our team would like to update you of an important change regarding TLS certificate pinning support in our SDKs.  On June 30, 2025, Amplitude will officially decommission support for TLS certificate pinning on the client side. While our SDKs have not supported pinning for several releases, we understand that a small subset of customers are still using legacy versions of our SDKs with pinning enabled. If you are one of these customers, we strongly encourage you to discontinue the use of pinning as soon as possible prior to June 30, 2025.  IMPORTANT: If you continue to rely on TLS certificate pinning after this date, then you will not be able to send data to Amplitude successfully. We understand that this change may be disruptive and apologize for the inconvenience. There are a few reasons this change is necessary:Because the intermediate certificates being pinned in our legacy SDK versions are not managed by Amplitude, certificate authorities may at any time stop signing our new certific

On February 24th, 2025 at 5PM PST, we will be renewing the SSL certificate used for api.amplitude.com and analytics.amplitude.com domains. We are only updating our end-entity certificate without any changes to our intermediate or root certificates. For the vast majority of situations, we do not expect any impact with sending data to Amplitude or using Amplitude. How do I know if I am impacted? To understand if you are impacted, please reach out to your team responsible for the Amplitude implementation (e.g. IT, Engineering, or the team who handles the Amplitude SDK) and send them the information within this post. If you answer yes to any of the three questions below, then you are impacted by this update and we will provide you with our new end-entity certificate. If you answer yes to question 2, we will additionally provide you with our entire chain of root and intermediate certificates. These scenarios are very rare and will not require action from the majority of customers.Do your sy

 Amplitude HEATMAPS in Closed BETA We’re excited to announce the launch of our Heatmapping feature for the web in Closed BETA! You can now view Click Maps, with Selector Maps and Scroll Maps coming soon—all linked to your Amplitude replays. Heatmaps visually represent user behavior, highlighting where users click, scroll, and engage the most. With Amplitude, you can combine these visual insights with your quantitative data, providing a clearer understanding of user engagement patterns and helping you optimize experiences effectively. We’re looking for participants who can set up Amplitude Session Replay (unlocking Heatmaps) within the next 2 weeks. This involves instrumenting or upgrading to the latest version of the Session Replay Standalone SDK or Plugin (bonus points if you’re already set up!).Interested?Reply to this thread or DM me with your email, Org ID, and Project ID, or reach out directly at brandon.khoo@amplitude.com with these details. I’ll send you a formal invite once I h

UPDATE: We appreciate all the feedback after our original announcement regarding switching to the updated Starter plan. We hear you and we’ve since made some changes.Customers coming from the legacy Starter plan will now continue to have unlimited saved charts, Projects, and Spaces on the new Starter plan.You can find the details for both Starter plans below (and anything that’s changed since the original announcement is italicized).  Hi everyone! This post is for users who created an organization on the Amplitude free plan (aka the Starter plan) before 8/27/2023. On 8/28/2023, we released a new version of the Starter plan to load our free plan with features (across analytics, experimentation, and audience management) that were previously only available on paid plans. The table below can help you see what’s changed from the legacy to the updated plan. Have thoughts on how these changes affect the way you use Amplitude? This is important for us to know, so please comment below or send m

Amplitude is constantly finding ways to enhance customer value.  Beginning February 1st, 2024, Amplitude will count Monthly Tracked Users (MTUs) at an organization level, instead of at a project level. This change may lead to a slight drop in your MTU count. How will the new MTU count work?Current MTU counting method: An MTU is a unique user who triggers one or more events in a project within a calendar month. MTU counting method after February 1st change: An MTU is a unique user who triggers one or more events in an organization within a calendar month.As Amplitude will dedupe users across the organization as opposed to a project, many customers may see a slight decrease in their MTU count as a result of this change.Does this change impact me?This MTU counting change applies to all organizations created after October 2017. If your account with Amplitude was created before October 2017 and your org ID is lower than 33746 (your org ID can be found on the Settings page), this change does

Hello Amplitude Community!My name is Jeremie, and I’m your community manager. We’re here to discuss Amplitude’s products in these categories, where you can search for answers, post questions, and overcome any roadblocks. You can also:  Subscribe to the latest product updates share product ideas,  help others, and become an Amp Champ! With this in mind, please introduce yourself by sharing (1) your name and title, (2) where you’re from, (3) and your hobbies and interests (beyond work, if you like!) Here’s a little more about me: Hello, I’m Jeremie! I’m joining the team with experience scaling digital customer experiences and building brand communities across industries. I am originally from France. My hobbies are travel, writing, and volunteerism. I’m still relatively new to the analytics space and can’t wait to make my work more data-driven with your help!  I look forward to meeting you all. Feel free to send me questions about this online forum and Amplitude community programs.

The Flutter SDK version 3.x integrates with the maintenance versions of the iOS and Android SDKs. The Android SDK entered its end-of-support phase starting from December 16, 2021. Similarly, the iOS SDK was placed into maintenance mode on October 27, 2023, and it is scheduled to transition to end-of-support status by October 27, 2024, at the earliest. For more information, refer to the Amplitude SDKs and Tools Maintenance & Support Policy.The Flutter SDK version 4.x is updated to wrap the latest Swift and Kotlin SDKs.Key features and benefits are: Unified interfaces across all the latest Amplitude analytics SDKs, facilitating consistent integration and functionality Default tracking feature supported to track “Sessions”, “App lifecycles”,“ Deep links” along with the corresponding configurations A log level setting added to configuration for easier debugging Better supports of the underlying Swift and Kotlin SDKs Begin your migration by consulting the migration guide and the c

Greetings, Amplitude Community!You can help make the Amplitude products even better by sharing your new and voting on existing product ideas!Here are a few tips when submitting feature requests: Use a precise title that summarizes your idea. One fantastic idea per post - if you have multiple ideas in mind, please create a different idea for each. Doing this will help us better manage and make sure that the statuses are reflected correctly. Before posting an idea, please be sure this is not something Amplitude is already capable of - search the community or our docs to see if this is already available or has already been requested. Details, details, details - explain the idea clearly, and provide some helpful context: What is the use case for this? What problem is it solving? Is this a critical blocker for you or is this something that would be nice to have? Other things to considerHow to create an idea and how to voteTo create an idea in the Amplitude Community, sim

Hi All:Excited to announce our first Tech Talk event. Topic is Elevate your Data Management, and it’s hosted by our trainers and a top-notch CSM who has worked with dozens of customers in streamlining their data management strategies. Sign up here in Amplitude Academy: https://academy.amplitude.com/amplitude-tech-talks

Starting from version 240a7, Aug 2023, we are updating the GTM client-side template for Amplitude (Amplitude Analytics Browser SDK). Specifically, we're moving from the Marketing Analytics SDK to the Amplitude Browser SDK 2.0. This transition brings enhanced support, better functionality, and new features.Key Benefits: Streamlined Configuration to make setting up Amplitude even easier. Advanced Campaign Tracking to gain deeper insights into marketing performance and optimization. Comprehensive Event Tracking to benefit from both default and upcoming feature releases. While this upgrade offers numerous advantages, there might be slight shifts in how your current analytics charts behave. However, we've made these changes configurable to maintain consistency. If you wish to retain the legacy behavior, it's essential to review the following list of breaking changes and adjust your configuration accordingly.Summary of changes: Page View event’s name and propertiesThe new template change

What happened?  As part of our vulnerability management program, we recently discovered an Amplitude image that was accidentally made publicly available on DockerHub. Through our investigation, we confirmed that the image included credentials for some third-party integrations, Redshift, and Snowflake for the Amplitude query add-on for certain Amplitude customers. Amplitude removed the image from public access within one hour of the discovery. At this time, there is no evidence that the credentials have been used maliciously.  How do I know if I was impacted? If your organization was impacted, your organization’s Amplitude admins were notified via email on Friday, May 12, 2023. If your admins did not receive an email, your organization was not impacted and no action is required.  What actions am I supposed to take? Please refer back to the notification email your organization's Amplitude admins received. We've outlined the specific actions your organization needs to take there. When

Hi all,We’ve begun the process of deprecating a few fields from our Export API in order to simplify the format and remove misleading/confusing information. Here is the list of affected fields. Note that to preserve backwards compatibility, these fields will continue to exist as keys in the JSON data, but their value will always be null.$schema: removed, an Amplitude-internal field. is_attribution_event: removed, an Amplitude-internal field. amplitude_event_type: removed, an Amplitude-internal field. device_manufacturer: removed, data is duplicated inside device_type/device_family. device_brand: removed, data is duplicated inside device_type/device_family. device_model: removed, data is duplicated inside device_type/device_family. user_creation_time: removed, an inaccurate timestamp. If you were using this field, please note that it is not an accurate value and will not match with the “New User” calculations in Amplitude. If you have an important business use case for this field, please

We’ve just rolled out a new experience to provide more contextual information about our data integrations (available in the product here).We’re also excited to announce a new public portal that allows you to vote and provide input on upcoming data integrations. You can add your integration cards to this portal and upvote the ones you want us to build! Your feedback will directly impact our development priorities and improve our product for you!Vote for your favorite integrations!

Today, we are excited to announce our new Analytics Go SDK and Ampli wrapper is out of beta and generally available.Features include:Amplitude Analytics SDK for Golang Full feature parity with other next generation SDKs, like custom plugin support. Ampli wrapper for GolangDocumentation: https://www.docs.developers.amplitude.com/data/sdks/go/GitHub: https://github.com/amplitude/analytics-goExamples: https://github.com/amplitude/analytics-go/tree/main/examplesReleases: https://github.com/amplitude/analytics-go/releasesAmpli wrapper: https://www.docs.developers.amplitude.com/data/sdks/go/ampli/

On Saturday February 18th, 2023 at 8AM PT, we will be renewing a certificate used for api.amplitude.com and analytics.amplitude.com domains. We are only updating our end-entity certificate without any changes to our intermediate or root certificates. For the vast majority of situations, we do not expect any impact with sending data to Amplitude or using Amplitude Analytics.How do I know if I’m impacted?To understand if you are impacted, please reach out to your team responsible for your Amplitude implementation (e.g. IT, Engineering, team who handles the Amplitude SDK) and send them the information present in this post.Have your team review the following information and if you answer yes to either of the two points below, then you are impacted. Your systems trusts only the current Amplitude end-entity certificate that is expiring on February 28th, 2023 Your systems pin the entire certificate chain The above scenarios are very uncommon and most users will not require action from this

We’ve updated the Source creation and configuration process to streamline workflows for Data Governors. These changes make it easier to quickly create Sources and start using them in planning without needing to determine technical implementation details ahead of time.The following items are impacted: Source creation in Data web app (Updated) Implementation page in Data (Removed) Ampli CLI pull command (Updated) configure command (Added) Requirements: Ampli CLI 1.30.0+ Adds the configure command Ampli CLI < 1.30.0 Full support for configured sources. Throws error on unconfigured sources, will prompt to update to the latest version of the CLI.   Overview of new workflow Creating a Source in Amplitude Data To create a new Source, start from the Catalog page (Data => Connections => Catalog ). However, you are no longer required to enter a Runtime at creation time. Just give your Source a name and you’re good to start using it in the Tracking Plan.When y