Over time, test properties, renamed attributes, and deprecated fields accumulate in your Appcues account. This guide walks through your options for cleaning them up — from self-serve steps in Studio to changes that require Support or developer involvement.

What you can and can't do today

Review and organize properties

Open Settings > Data > Properties in Studio. This page lists every user property and group property your account has received, including:

• Property name and data type
• Example values
• Whether the property is custom (sent by your team) or auto-collected by the Appcues SDK

Use this page to audit which properties are active and which are stale. If a property shows outdated example values or hasn't been sent recently, it's a candidate for cleanup.

To change which properties appear as display names for users and accounts throughout Studio, see Configure your account and user identifiers. This doesn't remove properties, but it makes Studio easier to navigate when your property list is cluttered.

For a full walkthrough of the Properties page, see View and manage your properties.

Remove properties from Studio

There is no self-serve option to remove individual properties from Studio today. If you have user or group properties cluttering your account that you no longer use, contact support@appcues.com with:

• Your Appcues Account ID
• The exact names of the properties you want removed

Stop collecting a property going forward

If a property is being sent by mistake, is duplicated, or is no longer needed, the most reliable way to stop it from appearing is to remove it from your code.

1. Locate every Appcues.identify() or Appcues.group() call that sends the property. Check your codebase, tag manager, and any integrations (Segment, HubSpot, etc.) that sync data to Appcues.
2. Remove the property from those calls and deploy the change.
3. The property remains in Studio for users who already have it set, but no new values will be recorded.

Removing a property from your code does not delete historical data. Users who previously received the property still have it on their profiles. To remove historical values, see the deletion options below.

Delete a user's entire profile

If you need to wipe a user's data entirely — for example, to remove a test user or fulfill a data deletion request — you have two API options.

Public API (single user)

Use the Appcues Public API to delete a specific user profile. This removes the user's properties and event history from Appcues.

See Schedule API user deletion with Postman for a step-by-step walkthrough.

GDPR Deletion API (bulk)

To submit deletion requests for multiple users at once, use the GDPR Deletion API. Pass a list of user IDs and Appcues processes them in bulk.

See GDPR Deletion API for endpoint details and request format.

Both deletion methods remove user profile data and events from Appcues. They do not remove user activity from aggregated analytics and reporting. Flow completion counts, for example, still reflect the deleted user's past activity.

What's not available today

The following operations are not currently supported as self-serve actions:

• Delete a property from all users — there is no way to remove a specific attribute (e.g., old_plan_name) across every user profile in bulk.
• Rename a property — if a property was sent with the wrong name, you cannot rename it in place. Instead, start sending the correct name and stop sending the old one.
• Manage ingestion filtering rules in Studio — the ability to block specific properties from being processed exists at the API level but is not configurable in Studio today.

If you need help with any of these, contact support@appcues.com and describe what you're trying to achieve. Support can advise on the best available solution.

If you're not sure what to clean up

Start by reviewing the Properties page in Studio. Look for:

• Duplicate properties — e.g., company_name and companyName that represent the same thing. Pick one, update your code to use it, and stop sending the other.
• Test properties — properties with names like test_field or values like asdf that were used during development.
• Stale auto-collected properties — properties the SDK collected automatically that you never use for targeting or segmentation.

Once you've identified what needs to go, use the steps above to take action — or contact Support if the cleanup requires changes you can't make self-serve.