Merge branch 'develop' of github.com:braze-inc/braze-docs into bf/rea…

…ct_GA_callouts

_docs/_user_guide/administrative/app_settings/manage_app_group/custom_event_and_attribute_management.md

@@ -34,12 +34,12 @@ Once you have created a **Custom Event** or **Product**, you can click **Manage
 To make these added custom attributes, events, products, or event properties trackable, you must ask your developer to create it in the SDK using the exact name you used to add it earlier. Or, you can use Braze's [APIs]({{site.baseurl}}/api/basics/) to import data on that attribute. After that, the custom attribute, event, or other will be actionable and apply to your users!
 
 {% alert note %}
-All User Profile data (custom events, custom attributes, custom data) is stored as long as those profiles are active.
+All user profile data (custom events, custom attributes, custom data) is stored as long as those profiles are active.
 {% endalert %}
 
 ## Blocklisting custom attributes, custom events, and products
 
-If you want to stop tracking a specific custom attribute, event, or product (e.g., accidental creation during testing, no longer useful), search for it in the **Custom Events** tab, then click **Blocklist**.
+To stop tracking a specific custom attribute, event, or product (e.g., accidental creation during testing, no longer useful), search for it in the **Custom Attributes**, **Custom Events**, or **Products** tab, then click **Blocklist**.
 
 To prevent collecting certain device attributes, see our [SDK guide][88].
 

_docs/_user_guide/data_and_analytics/custom_data/blocklist_delete_custom_data.md

@@ -10,40 +10,13 @@ description: "This reference article covers how to blocklist or delete custom ev
 
 > You may occasionally identify custom attributes, custom events, or purchase events that are either consuming too many data points, are no longer useful to your marketing strategy, or were recorded in error. To stop this data from being sent to Braze, you can blocklist a custom data object while your engineering team works to remove it from the backend of your app or website.
 
-The process to retire a custom data object looks like this:
-
-1. You [blocklist](#blocklisting-custom-data) the custom data object so it is no longer recorded.
-2. You remove the code from your deployments of the Braze SDK, CDP configurations, or other data sources (i.e., data sent from your backend to Braze via API) that record this custom data object.
-3. Your customer success manager or the Braze Support team delete the custom data object from the list of custom attributes, custom events, or purchase events.
-
 ## Blocklisting custom data
 
-Blocklisting prevents a particular custom data object from being recorded by Braze going forward.
-
-{% alert important %}
-Blocklisting does not remove data from user profiles or retroactively decrease the amount of data points incurred for that custom data object.
-{% endalert %}
-
-To blocklist a custom data object:
-
-1. In Braze, go to **Manage Settings**.
-2. Select the relevant page for the custom data object you want to blocklist: **Custom Attributes**, **Custom Events**, or **Products**.
-3. Find the custom data object in the table.
-4. Select **Blocklist**.
-
-{% alert note %}
-If you are using our [updated navigation]({{site.baseurl}}/navigation), you can find all of these pages under **Data Settings**.
-{% endalert %}
-
-![Warning that prevents you from blocklisting a custom data object and lists where the custom data is currently being referenced.][1]{: style="max-width:50%;float:right;margin-left:15px;"}
-
-If the custom data object is still in use, you need to remove it from the segment filters or campaign triggers it is referenced in before you can blocklist it. You can see where the custom data is currently in use when you attempt to blocklist it.
-
-If the custom data is being referenced in too many places, or if you want to blocklist many items at once, please reach out to support for help.
+Blocklisting prevents a particular custom data object from being recorded by Braze going forward. Blocklisting does not remove data from user profiles or retroactively decrease the amount of data points incurred for that custom data object. For specific details, refer to [Custom event and attribute management]({{site.baseurl}}/user_guide/administrative/app_settings/manage_app_group/custom_event_and_attribute_management/#blocklisting-custom-attributes-custom-events-and-products).
 
 ## Deleting custom data
 
-After you have blocklisted the custom data object and removed references to it from your app or website, your customer success manager or the Support team will delete the custom data.
+After you have blocklisted the custom data object and removed references to it from your app or website, the custom data will be deleted.
 
 Deleting custom data does the following:
 

_docs/_user_guide/data_and_analytics/custom_data/custom_attributes.md

@@ -23,7 +23,7 @@ If you are using our [updated navigation]({{site.baseurl}}/navigation), you can
 
 From this page, you can view, manage, or blocklist existing custom attributes, or create a new one. If you block a custom attribute, no data will be collected regarding that attribute, existing data will be unavailable unless reactivated, and blocklisted attributes will not show up in filters.
 
-If you would like to remove custom attributes from user profiles, set the value to "null" in your API request to the [`/users/track` endpoint]({{site.baseurl}}/api/endpoints/user_data/post_user_track#user-track).
+To remove custom attributes from user profiles, set the value to "null" in your API request to the [`/users/track` endpoint]({{site.baseurl}}/api/endpoints/user_data/post_user_track#user-track).
 
 ## Setting custom attributes
 
@@ -124,10 +124,10 @@ A date string such as "12-1-2021" or "12/1/2021" will be converted to a datetime
 {% alert important %}
 When segmenting using the **DOES NOT MATCH REGEX** filter, you must already have a custom attribute with a value assigned in that user profile. Braze suggests using "OR" logic to check if a custom attribute is blank to ensure users are being targeted properly.<br>
 
-More resources on regex:
-- [Regex with Braze]({{site.baseurl}}/user_guide/engagement_tools/segments/regex/)
-- [Regex Debugger and Tester](https://regex101.com/)
-- [Regex Tutorial](https://medium.com/factory-mind/regex-tutorial-a-simple-cheatsheet-by-examples-649dc1c3f285)
+More resources on regular expressions:
+- [Regular expressions with Braze]({{site.baseurl}}/user_guide/engagement_tools/segments/regex/)
+- [Regular expression debugger and tester](https://regex101.com/)
+- [Regular expression tutorial](https://medium.com/factory-mind/regex-tutorial-a-simple-cheatsheet-by-examples-649dc1c3f285)
 {% endalert %}
 
 ### Arrays {#arrays}
@@ -206,7 +206,7 @@ You can use nested custom attributes to send objects as a data type for custom a
 
 ### Arrays of objects
 
-Use an array of objects to group related attributes. For more information, refer to [Array of objects]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/array_of_objects/).
+Use an array of objects to group related attributes. For more details, refer to our article on [Array of objects]({{site.baseurl}}/user_guide/data_and_analytics/custom_data/custom_attributes/array_of_objects/).
 
 ## Purchase and revenue tracking {#purchase-revenue-tracking}