You can access the Settings page by clicking in the top right dropdown menu and selecting "Account Settings". Only organization admins and managers can access this page. Within the Settings page you can navigate between General, Users, Projects, and for admins, the Plan Admin page via the left sidebar.
Table of Contents
- Getting Started
- General
- Users
- Projects
- Create Project
- Project General Settings
- Events
- Custom Events
- Data Filters & Block List
- Event Properties
- User Properties
- Annotations
- Integrations
- Export Data
- Email Notifications (Enterprise)
- Plan Admin
- Usage Reports (Enterprise)
Getting Started
Creating an Organization
Amplitude organizes projects and users in 'organizations'. If you are the first person in your company to sign up for an account, you should create an organization using your company name.
Joining an Organization
If your company has already created an organization, then wait for an admin to add you so you can access your company's projects.
General
The default landing page in settings is the "General" section. To see your organization's users, you should select "Users" in the left sidebar. To navigate to your project's settings, you should select "Projects". Likewise, if you are an admin and need to view admin information you should go to the "Plan Admin" page. If you are an admin or a manager and you are interested in seeing how users in your organization are utilizing Amplitude, then you can visit the "Usage Reports" tab.
Profile
The profile box shows you your Organization, Role, Email, Name, and Password associated with your Amplitude account. You can click "EDIT" in the top right corner to change your display name as well as update your password.
Email Subscriptions (Enterprise)
This box shows all dashboards you have subscribed to via email. You can click into each individual dashboard directly from here, view the owner of the dashboard, change when you receive email reports, and select if you want to have CSV files sent attached to the report. Additionally, on hover you can click on the trashcan icon to remove your subscription to a particular dashboard.
Shared Links (Enterprise)
You can manage your shareable links in your organization's settings page under the "Shared Links" section. Here, you can click into the original chart, copy the URL, or revoke access to the URL. You can read more about Shared Links and how to create them here.
Users
At the top of the page you will see an overview of your organization, which includes the number of total users, joined users, and pending users. You can add users to the organization to access your projects by clicking the "Invite" button, typing their email into the text box, using the dropdown menu under "Role" to specify their permission level, and selecting their default project. Only admins and managers can add/remove users, and you can also add multiple users at once. The default project sets a new user's dropdown menus to that project when they first log into Amplitude. Going forward, the dropdown will switch to whichever last project you have used.
You can also select the team and the dashboards a new user will have pinned by default in your organization. The dashboards that will show up in the dropdown are the 10 dashboards that have been pinned the most within your organization.
An admin or manager can also adjust the user's organization role or permissions with the appropriate dropdown menu located beneath the 'Org Role' column. You can see all of your current users in the "Joined Users" view while the "Pending Users" shows users who have an outstanding invite. Additionally, you can remove users from your organization here as well by hovering over their email and clicking the "Remove" button.
NOTE: If you remove a user, all their content (charts, dashboards and cohorts) will be unassigned. However, admins can transfer the ownership of unassigned content to other users.
Bulk Transfer Ownership
Bulk Transfer Ownership is a feature that will allow you to transfer ownership of all inventory from one user to another. You can find this feature on the Team Members page on the top right under the button "Bulk Transfer Ownership".
Note: the transfer is permanent, so please use it with care. We recommend trying it with one user before doing it with many at once.
- A user's content will need to be transferred BEFORE they are deleted/revoked from the org. The ‘Source User’ must be an existing user in Amplitude in order to transfer ownership.
- Once a user’s content has been transferred, their access may be revoked and the user can be deleted.
- The 'Destination User' must have logged into Amplitude at least once prior to the transfer.
- If the ‘Destination User’ doesn’t have access to the project in which the content was created, the new owner will still not have access to the content, despite being the owner of said content. Permissions will NOT transfer. You will need to change these separately.
- Any charts, dashboards, cohorts & notebooks created by the source user will be transferred to the destination user.
Official Dashboards
Dashboards that are marked as "Official" in Settings will appear in sidebars of all users in that organization. This ensures that users have a direction to follow, especially when they log into Amplitude for the first time. We recommend marking your "source of truth" dashboards to be "Official" for other users in your company to easily follow.
Projects
The Projects tab shows you all the projects in your organization. This page shows you an overview of project information such as Project ID, API Key, and events collected this month. You can click into each individual project by using the "Manage" button next to each project's name.
Create Project
You can create a new project within your organization by clicking the green "Create Project" button. You will be prompted to name your project. For each project your company produces, we recommend making two projects in Amplitude with one for testing and one for production. This is because once data is recorded by Amplitude it cannot be deleted or modified. Our dashboards run off of numerous precomputed sets of data, which means it is expensive to remove or edit data once collected.
Project General Settings
- Project ID: This is the Project ID for the project.
- API Key: Your API Key, used for calling our APIs.
- Time Zone: Allows you to modify the time zone data is displayed in on charts in the platform, and Amplitude will shift the timestamps of the events to match the set time zone. The default time zone Amplitude uses is UTC (Universal Time Coordinated). The set time zone will impact all Amplitude users and queries, which includes the Dashboard Rest API. It will not affect the HTTP API or your raw data, as event ingestion will continue to be in UTC.
- Secret Key: Your project's Secret Key, used for calling our APIs.
- Event Types: Your project's current distinct count of event types sent to Amplitude.
- Event Properties: Your project's current distinct count of event properties sent to Amplitude.
- User Properties: Your project's current distinct count of user properties being sent to Amplitude.
- Events This Month: Number of events your project has sent to Amplitude this month.
- Events Last Month: Number of events your project has sent to Amplitude last month.
If you click "MANAGE" next to the project's name, then you can go into each project's individual settings. You can also change the name of your project by clicking on its name in that page or delete the project by clicking the "DELETE PROJECT" icon. Please note that deleted projects cannot be revived or renamed after deletion at this time. If you plan on reusing the project name, rename the project before deletion.
Events
Delete: Amplitude allows organization admins and managers to delete unwanted event types from projects. This is useful if you accidentally sent some new and unwanted event types or if you have exceeded your project's 2000 event type limit. To delete these events, select the events you want to delete and click "DELETE". IMPORTANT NOTE: The number you see to the left of the "Selected" is the number of events you have selected to delete. Please make sure you are only selecting the events you want to delete.
This will prompt you with some information and ask you to confirm the deletion by typing "DELETE # EVENT TYPES" in the input box, where # is the number of events that you have selected. Click on the "Delete # Event Types" button to finalize the deletion. IMPORTANT NOTE: Please make sure that the number you are entering is equal to the number of events you actually want to delete. If the number is not what you expect then that means you may have selected other events you do not want to delete.
Please note the following:
- Deleting events is permanent, irreversible, and immediate.
- If you do not want the deleted event type to count for historical active user counts or show up in any charts, then you should mark the event as "Inactive" before deleting it.
- It is not possible to delete historical data. All saved charts that contain the deleted event type will still show the deleted event type. If you no longer wish to see the deleted event type at all, then you should either archive all charts with that event type on it or remove the event type from the saved chart. Once removed, there will be no way to re-add the deleted event type to the saved chart as it will no longer show up in the dropdowns.
- Once an event type is deleted, Amplitude will block that event type and immediately stop collecting new data for it. Any incoming new data for that event type will not count towards your event volume.
- You will no longer be able to query on an event type once it has been deleted. It will no longer appear in dropdowns and you will not be able to create new charts with it.
- The deleted event type will no longer count towards your project's 2000 event type instrumentation limit.
- You should update your instrumentation to stop sending the deleted event type.
- If your project exceeded the instrumentation limit and event types were deleted to go back under the instrumentation limit, then it may take up to 24 hours for new event types to be indexed in the platform. So, if you send new event types to your project after cleaning up your instrumentation, you many not see the event types in the dropdown menus for up to 24 hours.
- Once the limit is reached for event types or properties, we will stop indexing the new values. New values sent while you were over the limit can only be accessed in the raw data e.g. exporting via CSV file or export API's.
- You can see event types that have been deleted from your project in the Block List tab.
- You cannot use the name of an event you deleted for a new event you plan to send.
Display Name: This is helpful if you want to rename a certain event. Note: If you give two events the same display name, they will NOT be combined or merged. In other words, there will be two events in the UI with the same name and they will be indistinguishable. Renaming events only affects our UI and does not change it in the raw data. If you have Redshift, you will have to query the event by its recorded or instrumented name.
Visibility: This is helpful for certain events such as push notifications that you want to track but do not want to visualize on the dashboard in any charts. Marking an event as "Hidden" does not delete the raw data. In addition, Enterprise customers will also always be able to query for hidden events via Redshift. You can choose to hide events from the dropdown menus, the Pathfinder chart, or the Personas report. This is useful if there are events you want to track but cause clutter in those specific chart types and are not useful to your analyses in Pathfinder or Personas.
Activity: This is helpful if you want dashboard metrics to stop counting certain events for any 'All Users', 'Active User', or 'Any Event' metric. For instance, if you mark an event 'OPEN' as "Inactive", users who send just the 'OPEN' event the next day will not be counted as an active user for that day. Note that inactive events will still count towards our new user definition. In addition, marking an event as "Inactive" is applied retroactively and immediately, e.g. historical data may change immediately. Inactive events will still count towards your event volume.
Properties: On hover, you can click on "Properties" which will bring up a separate window where you can view all event properties for that specific event. You have the option of marking them as "Visible" or "Hidden" here, which is helpful for certain event properties that you no longer want to see in the user interface. For example, the event property may not be in use anymore or might be a result of an instrumentation error. Note that marking an event property as "Visible" does not delete the raw data. Enterprise customers will also always be able to query for hidden event properties via Redshift.
Custom Events
Custom events are supported in the following charts and reports: Event Segmentation, Funnel Analysis, Retention Analysis, Stickiness, and Compass. You can segment custom events by properties that exist for all events within the custom event. They will have the prefix '[Custom]' before the event name in your charts. Note that you cannot query on custom events in Redshift. In the Custom Events section of your project's Settings page, you can create new events to analyze in the dashboard by combining one or more existing events (and event/user properties) into a single event. Only admins, managers, and members can create custom events.
Custom events can be used for determining if a user performed one or more events, such as viewing Landing Page A or Landing Page B. In addition to combining multiple events into a single event, you can also condition an added event by an event property or user property. To create a custom event, click the "+CUSTOM EVENT" button, which will bring up a separate window. Then, name your custom event and use the dropdown menus to add events and/or properties to it. You can view and edit the custom event definition by clicking on the event name. The below example shows a custom event that matches when a user performs the 'CompletedProfile' event OR the 'UserSignedUp'. Note: if the custom event was renamed, the updated custom event will need to be reselected on all charts associated with the previously named event.
Data Filters & Block List
You can block event types, event properties, and user properties during data processing using data filters. These changes are immediate and will stop the event data described below from being processed in the future. In addition to setting up the ingestion filter, we recommend making the appropriate changes in your instrumentation to stop sending the unwanted event data. IMPORTANT NOTE: You will NOT be able to recover blocked event data.
Please note the following:
- Data filters are applied immediately.
- Blocked event types are dropped, thus will not count towards your event volume limit
- Blocked event types will still count towards your 2000 unique event type limit.
- Blocked event properties are removed from events, but those events are still processed.
- Blocked user properties are removed from events, but those events are still processed.
- If a user already has a particular user property set, then blocking that user property will also unset it for all of that user's events going forward.
- When using the "equal to" operation to block event types, event properties and user properties, the value will need to be case sensitive for the filter to take effect.
Events Filters
| Attribute | Description |
|---|---|
| Name |
Equal to: Select a specific event type to block (e.g. ‘PlaySong’). Starts with: Select a prefix to block and all event types that match will be blocked (e.g. if you were to do ‘Add’ then the event types ‘AddFriend’ and ‘AddSong’ would be blocked). Is all numeric: Any events with an all numeric event type will be blocked (e.g. ‘1234’, ‘36’). |
| IP Address |
Equal to: You can enter specific IP addresses (e.g. 127.0.0.1) or IP networks using CIDR notation (e.g. 192.168.100.0/22) here and any events from those IPs will be blocked. |
| [Amplitude] Version |
Equal to: Block all events from a specific version of your app. Starts with: Block all events from versions that match a specific prefix. |
Event Properties Filters
After "for event type", select the event type for which you want to block event properties. If you select '[Amplitude] Any Event', then all event properties that match what you have selected will be blocked from all events.
| Attribute | Description |
|---|---|
| Property Name |
Equal to: Block an event property from all events or the selected event. Starts with: Block all event properties that match a specific prefix from all events or the selected event. Is Numeric: Block all numeric event properties from all events or the selected event. |
User Properties Filters
| Attribute | Description |
|---|---|
| Property Name |
Equal to: Block a user property from all events. Starts with: Block all user properties that match a specific prefix from all events. Is Numeric: Block all numeric user properties from all events. |
Block List
The Block List section shows you all the event types and user properties you are currently blocking for a specific project. You can also use this to unblock anything you have previously blocked. Additionally, you can view a history of all blocked event types and user properties here. The Block List will also show you event types that have been deleted from your project.
Event Properties
The Event Properties tab displays all event properties that have been instrumented for a particular project. From this view, you can also delete event properties. Amplitude allows organization admins and managers to delete unwanted event properties from projects. This is useful if you accidentally sent some new and unwanted event properties or if you have exceeded your project's 2000 event property limit. To delete these event properties, select the event properties you want to delete and click "DELETE". IMPORTANT NOTE: The number you see to the left of the "Selected" is the number of event properties you have selected to delete. Please make sure you are only selecting the event properties you want to delete.
This will prompt you with some information and ask you to confirm the deletion by typing "DELETE # EVENT PROPERTIES" in the input box, where # is the number of event properties that you have selected. Click on the "Delete # Event Properties" button to finalize the deletion. IMPORTANT NOTE: Please make sure that the number you are entering is equal to the number of event properties you actually want to delete. If the number is not what you expect then that means you may have selected other event properties you do not want to delete.
Please note the following:
- Deleting event properties is permanent, irreversible, and immediate.
- You cannot delete an event property for only some events. If an event property is an event property for multiple events, then it will be deleted across all those events.
- It is not possible to delete historical data. All saved charts that contain the deleted event property will still show the deleted event property. If you no longer wish to see the deleted event property at all, then you should either archive all charts with that event property on it or remove the event property from the saved chart. Once removed, there will be no way to re-add the deleted event property to the saved chart as it will no longer show up in the dropdowns.
- Once an event property is deleted, Amplitude will block it and immediately stop collecting new data for it.
- You will no longer be able to query on an event property once it has been deleted. It will no longer appear in dropdowns and you will not be able to create new charts with it.
- The deleted event property will no longer count towards your project's 2000 event property instrumentation limit.
- You should update your instrumentation to stop sending the deleted event property.
- If your project exceeded the instrumentation limit and event properties were deleted to go back under the instrumentation limit, then it may take up to 24 hours for new event properties to be indexed in the platform. So, if you send new event properties to your project after cleaning up your instrumentation, then you many not see the event properties in the dropdown menus for up to 24 hours.
- Once the limit is reached for event types or properties, we will stop indexing the new values. New values sent while you were over the limit can only be accessed in the raw data e.g. exporting via CSV file or export API's.
- You can see event properties that have been deleted from your project in the Block List tab.
- You cannot use the name of an event property you deleted for a new event property you plan to send.
User Properties
The User Properties section allows user properties to be hidden from all graphs and calculations in the platform. This is helpful for user properties that are old or that you no longer care to track. Marking a user property as "Hidden" does not delete the raw data. Enterprise customers will also always be able to query Redshift for the hidden user properties.
From this view, you can also delete user properties. Amplitude allows organization admins and managers to delete unwanted user properties from projects. This is useful if you accidentally sent some new and unwanted user properties or if you have exceeded your project's 1000 user property limit. To delete these event properties, select the user properties you want to delete and click "DELETE". IMPORTANT NOTE: The number you see to the left of the "Selected" is the number of user properties you have selected to delete. Please make sure you are only selecting the user properties you want to delete.
This will prompt you with some information and ask you to confirm the deletion by typing "DELETE # USER PROPERTIES" in the input box, where # is the number of user properties that you have selected. Click on the "Delete # User Properties" button to finalize the deletion. IMPORTANT NOTE: Please make sure that the number you are entering is equal to the number of user properties you actually want to delete. If the number is not what you expect then that means you may have selected other user properties you do not want to delete.
Please note the following:
- Deleting user properties is permanent, irreversible, and immediate.
- You cannot delete Amplitude's default-tracked user properties (prefixed by '[Amplitude]'). If you no longer wish to see those properties for your project, you should hide them.
- Once a user property has been deleted, it will be removed for all users who previously had that particular user property set. All existing events will still contain that user property (since historical data cannot be deleted) but their subsequent events will not contain that user property.
- It is not possible to delete historical data. All saved charts that contain the deleted user property will still show the deleted user property. If you no longer wish to see the deleted user property at all, then you should either archive all charts with that user property on it or remove the user property from the saved chart. Once removed, there will be no way to re-add the deleted user property to the saved chart as it will no longer show up in the dropdowns.
- Once an user property is deleted, Amplitude will block it and immediately stop collecting new data for it.
- You will no longer be able to query on an user property once it has been deleted. It will no longer appear in dropdowns and you will not be able to create new charts with it.
- The deleted user property will no longer count towards your project's 1000 user property instrumentation limit.
- You should update your instrumentation to stop sending the deleted user property.
- If your project exceeded the instrumentation limit and user properties were deleted to go back under the instrumentation limit, then it may take up to 24 hours for new event properties to be indexed in the platform. So, if you send new user properties to your project after cleaning up your instrumentation, then you many not see the user properties in the dropdown menus for up to 24 hours.
- Once the limit is reached for user properties, we will stop indexing the new values. New values sent while you were over the limit can only be accessed in the raw data e.g. exporting via CSV file or export API's.
- You can see user properties that have been deleted from your project in the Block List tab.
- You cannot use the name of a user property you deleted for a new user property you plan to send.
Annotations
Here, you can manage the annotations you have created via Microscope. You can click on the name of the annotation to edit the date, name, and description. Annotations are useful for keeping track of important dates across your charts in Amplitude. Only admins and managers can create annotations.
You can also remove and add new annotations here as well.
Integrations
Here, you can enter in the different keys for various different integrations. In order to see verified revenue data, you must input your Amazon, Google Play, or iTunes information in here.
Export Data
In the upper right-hand corner of your project's settings page, you will see an option to "Export Data". This feature allows you to download a zipped archive of JSON files over the specified time range.
Email Notifications (Enterprise)
The Email Notifications tab allows you to change your email notification settings for our collaboration features. Here, you can enable or disable email notifications for the following:
- Mentioned in a Comment: This will send you an email when you are mentioned in a comment.
- Received a Comment: This will send you an email when someone comments on one of your charts or dashboards.
- Received a Dashboard Proposal: This will send you an email when someone proposes a chart to a dashboard you own.
Plan Admin
Organization admins can use this page to view plan and event information. Amplitude currently has three available plans: Starter (Free), Elite, and Enterprise. Upgrading to the Enterprise plan gives access to the following additional features: Behavioral Cohorts, direct SQL access to data in Amazon Redshift, custom integration, and visualization compatibility. You also have the option to upgrade your plan or update your payment information on this page.
SSO (Enterprise)
Amplitude has integrations with Okta and G Suite for SSO. You can set up these integrations through the Plan Admin page. If you are interested in setting up SSO, then please reach out to your dedicated Success Manager or submit a request here.
Event Quota Alerts (Enterprise)
If you are an Enterprise customer, then the Plan Admin tab will show some additional information regarding your contract as well as your event volume quota. This will help you track your event volume usage right within the product. The top section will display your contract start and end date, your event limit, events seen this month, and events seen last month.
Email alerts will be sent to Admins at 80/90/100/110% of event quotas.
At the bottom of the page is a chart that shows you your current event volume. The black line marks your event volume limit. The red line shows the percentage at which you have set your event volume alert, which you can set by clicking the red alert button on the right. When the alert is triggered, all plan admins will receive an email notifying them. The solid blue line shows your current event volume and the dotted blue line shows expected event volume according to your event volume limit.
Usage Reports (Enterprise)
If you are an Enterprise customer and are an organization admin or manager, then there will be another tab called "Usage Reports". This tab will show you several usage reports and contains useful information about how users within your organization are utilizing Amplitude. The top box will show you the total number of users that have been invited to your organization, the number of joined users, pending users, dashboards, charts, cohorts, and shared links created.
The next two panels will show you your weekly active users and total queries run in the last 4 weeks.
Finally, the last two panels will show you the top 10 most active users as well as the most popular events performed by the users in your organization in the last 30 days.
