Manage your Amplitude Data settings

On the Settings page, you can:

• Name your project and specify the naming conventions you use for events and properties.
• Specify whether you 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.

These settings and features appear on five tabs: General, Environments, Integrations, API Tokens, and Schema Settings. This article describes each tab.

Roles and permissions in Amplitude Data

You can also restrict data management access while keeping permissions the same for other areas of Amplitude. Refer to The Permissions tab for more details.

General

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

Naming conventions

Amplitude Data requires a consistent naming convention for events and properties. Without one, your tracking plan becomes harder to read and manage, because multiple events or properties can share the same name with different capitalization.

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, require team reviews for changes made to main. With this option, make any changes to your tracking plan in a branch other than main. Specify the number of reviewers required for approval, up to seven.

Public link to your tracking plan

To share your tracking plan, use the public link on the General tab. Copy it to your clipboard and paste it into an email or Slack message. Stakeholders can read it but can't make changes.

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

Integrations

Integrate Amplitude Data with existing tools to streamline your analytics workflow. To integrate a platform, 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 password. Tokens authorize applications to use the same roles and permissions you have when you log in personally.

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

Click Copy to clipboard immediately, because you can't retrieve the token later.

Schema Settings

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, meaning your schema doesn't account for the received data. This usually happens when you don't plan for a particular data type or value when first setting up your schema.

Configure your schema settings to tell Amplitude how to handle these situations.

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

Click Save to apply any changes to your schema settings.

The Permissions tab

Data permissions restrictions limit who can perform Data Management functions. For example, you might want most 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, add restrictions for selected roles to limit data management access while keeping other permissions unchanged for those roles.

Under Restrict access in Amplitude Data, choose 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. Only administrators can access the Permissions tab.

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 let you change the configuration of the Analytics Browser SDK directly from within Amplitude, so you can make changes without code changes or releases. These settings merge with any configuration you defined locally in your SDK initialization code on your website.

Availability

Autocapture settings are available on projects that use version 2.10.0 or higher of the Amplitude Browser SDK with fetchRemoteConfig 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, the SDK retrieves configuration settings from Amplitude's servers using the project's API key. These remote settings merge with any local configuration you defined on your site. After merging, the SDK completes its initialization 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 don'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:

Zoning Insights also uses element interaction data to analyze engagement within defined areas of your pages. To use Zoning Insights, enable element interactions (and optionally configure allowlists) here or in your Browser SDK initialization.