Suppress and delete user data in accordance with your user suppression policies.
RudderStack’s User Suppression API lets you create regulations to suspend data collection and delete data for specific users. These regulations can be applied across multiple destination integrations simultaneously, simplifying the process of implementing compliance requests.
For example, if a user updates their preferences to opt-out of being tracked, you can implement a regulation in the User Suppression API that stops RudderStack from collecting their data at the source, and ensuring no data is sent to downstream destinations. Also, if the user requests to be forgotten, you can delete their data from multiple downstream destinations like Amplitude and Braze with one API call.
What are user suppression and user deletion?
To comply with data regulation statutes and users’ privacy choices, the User Suppression API lets you:
Suppress incoming source data for a user or list of users.
Delete collected data for users that reside in a given destination or across multiple destinations.
Suppression across multiple sources
You can leverage the User Suppression API to suppress all incoming data for a given user. RudderStack drops the events for that user at the source of collection. Suppression applies across all sources, however you can also specify the specific sources you want to suppress.
Specifying source and destination IDs in your regulation
When creating user suppressions with our API, you may wish to name specific sources for a suppress regulation, and specific destinations for a suppress and delete regulation. To do so, you must first obtain the source and/or destination IDs.
Retrieving source and destination IDs
Retrieve source and destination IDs from your RudderStack dashboard or by using the /v2/sources and /v2/destinations endpoints:
A successful response returns a 204 No Content status.
Post regulation requests are rate limited.
Limit (tokens per hour)
In the case of suppression, 1 user is equivalent to 1 token. For deletion, RudderStack calculates the number of tokens by multiplying the number of users with the number of destinations. For example, if there are n users with m destinations, the total number of tokens would be n * m.
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
for the working of basic functionalities of the website. We also use third-party cookies that
analyze and understand how you use this website. These cookies will be stored in your browser
consent. You also have the option to opt-out of these cookies. But opting out of some of these
have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.