Skip to main content

We are currently exploring the possibility of changing our project names within Amplitude and would like to seek your valuable insights on this matter.

Our primary concern is whether there are any potential side effects that may arise as a result of renaming our projects. We want to ensure a seamless transition and avoid any unintended impacts on our data and analytics.

Additionally, we are keen to know if Amplitude provides any official documentation or guidelines regarding the process of renaming projects, as well as any caveats or best practices associated with this change.

Hi @Arthur Alagao 

Renaming a project doesn’t have any impact on your underlying data and the charts. A project is identified largely on the project ID and the associated API key, which is critical to routing your ingested data correctly.

An ideal best practice would be to clearly communicate this project’s name change to your team and stakeholders who use Amplitude regularly. As far as naming conventions go, I would include the following parameters for easy identification

  • product name
  • if it’s web app vs iOS/android
  • prod or staging env

    Hope this helps.

 

Agreed on the above!

Make sure to also update the Data environment names to avoid any confusion between Analytics & Data

And make sure project name changes are also reflected in any necessary portfolio name changes, if your org utilizes portfolios. 

Reply


Terms & ConditionsCookie settings