Manage your Amplitude Data settings

In the Settings page, you can:

• Name your project, and specify the naming conventions you’ll use for events and properties
• Specify whether you’ll require team reviews for all changes to main
• Set the Amplitude projects for your environments
• Add integrations
• Generate API tokens
• Delete your Amplitude Data project

Find these settings and features on five different tabs: General; Environments; Integrations; API Tokens; and Schema Settings. This article describes each tab below.

Roles and permissions in Amplitude Data

You may also restrict data management access while keeping permissions the same for other areas of Amplitude. See The Permissions Tab for more details.

General

The General tab is where you’ll give your project a name, set the event and property naming conventions, set team review requirements for making changes on main, and delete your project. It’s also where you’ll find a public link to a read-only version of your tracking plan, so you can easily and safely share it with stakeholders across your organization.

Naming conventions

Amplitude Data requires you to set a consistent naming convention for events and properties. Without one, your tracking plan can become much harder to read and manage, as there could be multiple events or properties using the same name with different capitalization rules.

Specify a custom naming convention, or choose from the following:

• lower case
• Sentence case
• Title Case
• CamelCase
• lowerCamelCase
• snake_case

Team reviews

For larger teams and organizations, it’s good practice to require team reviews for any changes made to main. With this option, you must make any changes to your tracking plan in a branch other than main. You can specify the number of reviewers required for approval—up to seven—here as well.

Public link to your tracking plan

If you ever want to share your tracking plan, you can do so using the public link provided here on the General tab. Just copy it to your clipboard and paste it into an email or Slack message. Stakeholders can read it, but they can’t make any changes themselves.

You can also enable or disable the public link, which changes the availability for the selected project. Just click Create Public Link or Delete Public Link.

Integrations

You can integrate Amplitude Data with your existing tools to streamline your analytics workflow. To integrate a platform, simply click Connect or Add next to its name.

API Tokens

Use API tokens to authenticate to Amplitude Data using credentials other than your email address and a password. Tokens authorize applications to enjoy the same roles and permissions granted to you when you log in personally.

To create an API token, click Create Token. Amplitude Data generates the token and display it in a modal window.

Be sure to click Copy to clipboard now, as you won’t be able to retrieve the token later.

Schema Settings

Sometimes, Amplitude Data might receive data from your app that it doesn't know what to do with. This is usually the result of a **schema violation,**and it means the received data isn't accounted for in your schema. This is usually the result of failing to plan for that particular data type or value when you first set up your schema.

You can tell Amplitude how to handle these situations by configuring your schema settings.

For any unplanned events, event properties, event property types, user properties, or user property types, you can tell Amplitude Data to either mark them as unexpected, or to reject them outright. Amplitude Data ingests any events or properties marked as unexpected and send a notification to everyone subscribed to this schema. If you choose to reject unexpected data, however, Amplitude Data doesn't ingest or store the rejected data. Subscribers still receive a notification.

Click Save to implement any changes you make to your schema settings.

The Permissions tab

With data permissions restrictions, you can limit who can perform Data Management functions. For example, you might want most of your users to have the Member role so they can create dashboards and charts, but limit custom event creation and other data management features to managers or administrators.

In the permissions tab, you can add additional restrictions for selected roles, limiting data management access while keeping other permissions unchanged for those roles.

Under Restrict access in Amplitude Data, specify from the following options to restrict permissions to the viewer level on a per-project basis:

• Use Default Restrictions
• Restrict Members
• Restrict Members and Managers

Then, click Save.

Permission restrictions are available for Enterprise customers only and the Permissions tab is only visible to administrators.

Copy to other projects

Click Copy to Other Projects to apply the current permission restriction settings to another project.

Autocapture

The Autocapture settings in Amplitude Data allow you to change the configuration of the Analytics Browser SDK directly from within Amplitude, enabling you to make changes without code changes or releases. These settings are merged with any configuration you've defined locally in your SDK initialization code on your website.

Availability

Autocapture settings are enabled on projects that use version 2.10.0 or higher of the Amplitude Browser SDK where the SDK has fetchRemoteConifg enabled.

To disable remote configuration, set fetchRemoteConfig to false. Disabling fetchRemoteConfig doesn't disable the remote configuration options in Data Settings.

How it works

When the SDK initializes with fetchRemoteConfig enabled, it retrieves configuration settings from Amplitude's servers using the project's API key. These remote settings merge with any local configuration you define on your site. After merging, the SDK completes its initialization process along with any plugins using this combined configuration. Remote configuration doesn't impact the load time of pages on your site, but may impact SDK initialization time.

On the Settings Page, each configuration category offers three options:

• Default: Keeps the local configuration in the SDK as-is. Settings in the UI doesn't override it.
• On: Overrides the local configuration and sets the category to true. All settings within the category (for example, Element Interactions) follow the configuration in the UI.
• Off: Overrides the local configuration and sets the category to false.

Changes made through the UI take effect after 10 minutes.

Element interactions

When you enable Element Interactions, several options appear: