Deploy - April 11, 2023

_docs/_api/basics.md

@@ -297,7 +297,7 @@ Making a Braze-to-Braze webhook and using allowlisting? Check out our list of [I
 
 If you're implementing Braze using Ruby, you can use our [Ruby client library](https://github.com/braze-inc/braze-api-client-ruby) to reduce your data import time. A client library is a collection of code specific to one programming language—in this case, Ruby—that makes it easier to use an API.
 
-The Ruby client library supports the [User Endpoints]({{site.baseurl}}/api/endpoints/#user-data).
+The Ruby client library supports the [User Endpoints]({{site.baseurl}}/api/endpoints/user_data).
 
 {% alert note %}
 This client library is currently in beta. Want to help us make this library better? Send us feedback at [smb-product@braze.com](mailto:smb-product@braze.com).

_docs/_api/endpoints/export/user_data/post_users_global_control_group.md

@@ -104,9 +104,9 @@ The following is a list of valid `fields_to_export`. Using `fields_to_export` to
 |---|---|---|
 | `apps` | Array | Apps this user has logged sessions for, which includes the fields:<br><br>- `name`: app name<br>- `platform`: app platform, such as iOS, Android, or Web<br>- `version`: app version number or name <br>- `sessions`: total number of sessions for this app<br>- `first_used`: date of first session<br>- `last_used`: date of last session<br><br>All fields are strings. |
 | `attributed_campaign` | String | Data from [attribution integrations]({{site.baseurl}}/partners/message_orchestration/attribution), if set up. Identifier for a particular ad campaign. |
-| `attributed_source` | String | Data from [attribution integrations]({{site.baseurl}}<br>/partners/message_orchestration/attribution<br>), if set up. Identifier for the platform the ad was on. |
-| `attributed_adgroup` | String | Data from [attribution integrations]({{site.baseurl}}<br>/partners/message_orchestration/attribution<br>), if set up. Identifier for an optional sub-grouping below campaign. |
-| `attributed_ad` | String | Data from [attribution integrations]({{site.baseurl}}<br>/partners/message_orchestration/attribution<br>), if set up. Identifier for an optional sub-grouping below campaign and adgroup. |
+| `attributed_source` | String | Data from [attribution integrations]({{site.baseurl}}/partners/message_orchestration/attribution), if set up. Identifier for the platform the ad was on. |
+| `attributed_adgroup` | String | Data from [attribution integrations]({{site.baseurl}}/partners/message_orchestration/attribution), if set up. Identifier for an optional sub-grouping below campaign. |
+| `attributed_ad` | String | Data from [attribution integrations]({{site.baseurl}}/partners/message_orchestration/attribution), if set up. Identifier for an optional sub-grouping below campaign and adgroup. |
 | `braze_id` | String | Device-specific unique user identifier set by Braze for this user. |
 | `country` | String | User's country using [ISO 3166-1 alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) standard. |
 | `created_at` | String | Date and time for when the user profile was created, in ISO 8601 format. |

_docs/_api/endpoints/export/user_data/post_users_segment.md

@@ -115,9 +115,9 @@ The following is a list of valid `fields_to_export`. Using `fields_to_export` to
 |---|---|---|
 | `apps` | Array | Apps this user has logged sessions for, which includes the fields:<br><br>- `name`: app name<br>- `platform`: app platform, such as iOS, Android, or Web<br>- `version`: app version number or name <br>- `sessions`: total number of sessions for this app<br>- `first_used`: date of first session<br>- `last_used`: date of last session<br><br>All fields are strings. |
 | `attributed_campaign` | String | Data from [attribution integrations]({{site.baseurl}}/partners/message_orchestration/attribution), if set up. Identifier for a particular ad campaign. |
-| `attributed_source` | String | Data from [attribution integrations]({{site.baseurl}}<br>/partners/message_orchestration/attribution<br>), if set up. Identifier for the platform the ad was on. |
-| `attributed_adgroup` | String | Data from [attribution integrations]({{site.baseurl}}<br>/partners/message_orchestration/attribution<br>), if set up. Identifier for an optional sub-grouping below campaign. |
-| `attributed_ad` | String | Data from [attribution integrations]({{site.baseurl}}<br>/partners/message_orchestration/attribution<br>), if set up. Identifier for an optional sub-grouping below campaign and adgroup. |
+| `attributed_source` | String | Data from [attribution integrations]({{site.baseurl}}/partners/message_orchestration/attribution), if set up. Identifier for the platform the ad was on. |
+| `attributed_adgroup` | String | Data from [attribution integrations]({{site.baseurl}}/partners/message_orchestration/attribution), if set up. Identifier for an optional sub-grouping below campaign. |
+| `attributed_ad` | String | Data from [attribution integrations]({{site.baseurl}}/partners/message_orchestration/attribution), if set up. Identifier for an optional sub-grouping below campaign and adgroup. |
 | `braze_id` | String | Device-specific unique user identifier set by Braze for this user. |
 | `country` | String | User's country using [ISO 3166-1 alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) standard. |
 | `created_at` | String | Date and time for when the user profile was created, in ISO 8601 format. |

_docs/_api/endpoints/preference_center/put_update_preference_center.md

@@ -21,9 +21,12 @@ description: "This article outlines details about the Update a preference center
 This endpoint has a rate limit of 10 requests per minute, per app group.
 
 ## Path parameters
+
 | Parameter | Required | Data Type | Description |
 | --------- | ---------| --------- | ----------- |
 |`preferenceCenterExternalID`| Required | String | The ID for your preference center. |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3  .reset-td-br-4}
+
 
 ## Request body
 

_docs/_api/endpoints/subscription_groups/post_update_user_subscription_group_status_v2.md

@@ -22,7 +22,7 @@ You can access a subscription group's `subscription_group_id` by navigating to t
 
 If you want to see examples or test this endpoint for **Email Subscription Groups**:
 
-{% apiref postman %}hhttps://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#b1b9a0e0-6329-4df2-a465-53347f410662 {% endapiref %}
+{% apiref postman %}https://documenter.getpostman.com/view/4689407/SVYrsdsG?version=latest#b1b9a0e0-6329-4df2-a465-53347f410662 {% endapiref %}
 
 If you want to see examples or test this endpoint for **SMS Subscription Groups**:
 

_docs/_api/objects_filters/event_object.md

@@ -42,8 +42,8 @@ Tracking Custom Events article:
 }
 ```
 
-- [External User ID][23]
-- [App Identifier][21]
+- [External User ID]({{site.baseurl}}/api/basics/#user-ids)
+- [App identifier]({{site.baseurl}}/api/identifier_types/)
 - [ISO 8601 Time Code Wiki][22]
 
 #### Update existing profiles only

_docs/_api/objects_filters/messaging/email_object.md

@@ -35,7 +35,7 @@ description: "This reference article explains the different components of Braze'
 }
 ```
 
-- [App Identifier]({{site.baseurl}}/api/api_key/#the-app-identifier-api-key)
+- [App identifier]({{site.baseurl}}/api/identifier_types/)
 - For more information and best practices on pre-headers, see our help article on [email body styling][46].
 
 {% alert warning %}

_docs/_api/objects_filters/messaging/sms_object.md

@@ -21,4 +21,4 @@ description: "This reference article explains the different components of Braze'
 }
 ```
 
-- [App Identifier]({{site.baseurl}}/api/api_key#the-app-identifier-api-key)
+- [App identifier]({{site.baseurl}}/api/identifier_types/)

_docs/_api/objects_filters/messaging/whats_app_object.md

@@ -28,7 +28,7 @@ description: "This reference article explains the different components of Braze'
 }
 ```
 
-- [App identifier]({{site.baseurl}}/api/api_key#the-app-identifier-api-key)
+- [App identifier]({{site.baseurl}}/api/identifier_types/)
 
 ## Header variables object
 

_docs/_api/objects_filters/purchase_object.md

@@ -39,8 +39,8 @@ A purchase object is an object that gets passed through the API when a purchase
 }
 ```
 
-- [External User ID][23]
-- [App Identifier][21]
+- [External User ID]({{site.baseurl}}/api/basics/#user-ids)
+- [App identifier]({{site.baseurl}}/api/identifier_types/)
 - [ISO 4217 Currency Code Wiki][20]
 - [ISO 8601 Time Code Wiki][22]
 

_docs/_developer_guide/platform_integration_guides/android/initial_sdk_setup/android_sdk_integration.md

@@ -14,7 +14,7 @@ search_rank: 4
 > This reference article covers how to integrate the Android SDK into your Android or FireOS application. Installing the Braze SDK will provide you with basic analytics functionality and working in-app messages with which you can engage your users.
 
 {% alert note %}
-For optimal performance on Android 12, we recommend upgrading to [Braze Android SDK v13.1.2+](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#1312) as soon as possible. For more information, see our [Android 12 upgrade guide]({{site.baseurl}}/developer_guide/platform_integration_guides/android/android_12/).
+For optimal performance on Android 12, we recommend upgrading to [Braze Android SDK v13.1.2+](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#1312) as soon as possible. For more information, see our [Android 12 upgrade guide]({{site.baseurl}}/android_12/).
 {% endalert %}
 
 ## Step 1: Integrate the Braze library

_docs/_developer_guide/platform_integration_guides/cordova/cordova_integration.md

@@ -89,6 +89,6 @@ If you would like to log purchases at the order level instead of the product lev
 News Feed is being deprecated. Braze recommends that customers who use our News Feed tool move over to our Content Cards messaging channel—it's more flexible, customizable, and reliable. Check out the [migration guide]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/migrating_from_news_feed/) for more.
 {% endalert %}
 
-See the [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/news_feed/#news-feed) and [iOS]({{ site.baseurl }}/developer_guide/platform_integration_guides/ios/news_feed/) integration instructions for information on how to integrate the News Feed into your Cordova app. Alternatively, our Cordova plugin provides a method, `launchNewsFeed`, that will launch a modal News Feed without further integration. 
+See the [Android]({{site.baseurl}}/developer_guide/platform_integration_guides/android/news_feed/integration/) and [iOS]({{ site.baseurl }}/developer_guide/platform_integration_guides/ios/news_feed/) integration instructions for information on how to integrate the News Feed into your Cordova app. Alternatively, our Cordova plugin provides a method, `launchNewsFeed`, that will launch a modal News Feed without further integration. 
 
 The Braze Cordova SDK has several methods to get the number of read or unread News Feed cards for different categories. Check out a [sample project implementation](https://github.com/Appboy/appboy-cordova-sdk/blob/master/sample-project/www/js/index.js) for an example.

_docs/_developer_guide/platform_integration_guides/cordova/initial_sdk_setup/ios.md

@@ -61,7 +61,7 @@ To enable the automatic collection of the [iOS IDFA][3], set the following confi
 
 ### Location collection and geofences
 
-To enable location collection and Braze Geofences, use the [`geofence-branch`][3] instead of the default `master` branch. By default, the Braze SDK disables location collection and Braze Geofences. Additionally, use the following preferences configuration:
+To enable location collection and Braze Geofences, use the `geofence-branch` instead of the default `master` branch. By default, the Braze SDK disables location collection and Braze Geofences. Additionally, use the following preferences configuration:
 
 ```xml
 <platform name="ios">

_docs/_developer_guide/platform_integration_guides/flutter/flutter_sdk_integration.md

@@ -19,7 +19,7 @@ You will need to complete installation steps on both platforms separately.
 
 ## Prerequisites
 
-To complete the installation, you will need the [app identifier API key][3] as well as the [SDK endpoint][4]. Both are located under **Manage Settings** in the dashboard.
+To complete the installation, you will need the [app identifier API key]({{site.baseurl}}/api/identifier_types/) as well as the [SDK endpoint][4]. Both are located under **Manage Settings** in the dashboard.
 
 Before following these steps, install and set up the [Flutter SDK][5].
 

_docs/_developer_guide/platform_integration_guides/ios/advanced_use_cases/locations_and_geofences.md

@@ -11,8 +11,6 @@ Tool:
 
 # Locations and geofences
 
-Geofences are only available in select Braze packages. For access, create a [support ticket][support] or speak with your Braze customer success manager.
-
 To support geofences for iOS:
 
 1. Your integration must support background push notifications.

_docs/_developer_guide/platform_integration_guides/react_native/react_sdk_setup.md

@@ -13,7 +13,7 @@ search_rank: 1
 
 You will need to complete installation steps on both platforms separately.
 
-To complete the installation, you will need the [App Identifier API key]({{site.baseurl}}/api/api_key/#the-app-identifier-api-key) as well as the [SDK endpoint]({{site.baseurl}}/api/basics/#endpoints). Both are located under **Manage Settings** in the dashboard.
+To complete the installation, you will need the [app identifier API key]({{site.baseurl}}/api/identifier_types/) as well as the [SDK endpoint]({{site.baseurl}}/api/basics/#endpoints). Both are located under **Manage Settings** in the dashboard.
 
 ## Prerequisites and compatibility 
 Braze React Native SDK v1.38.0+:

_docs/_developer_guide/platform_integration_guides/swift/advanced_use_cases/locations_and_geofences.md

@@ -12,8 +12,6 @@ Tool:
 
 # Locations and geofences
 
-Geofences are only available in select Braze packages. For access, create a [support ticket][support] or speak with your Braze customer success manager.
-
 To support geofences for iOS:
 
 1. Your integration must support background push notifications.

_docs/_developer_guide/platform_integration_guides/unity/push_notifications/android.md

@@ -125,4 +125,4 @@ For setup guidance, visit [Deep Linking to In-App Resources][26].
 [61]: {{site.baseurl}}/developer_guide/platform_integration_guides/unity/advanced_use_cases
 [62]: {% image_buster /assets/img/unity/android/unity_android_push_settings_config.png %} "Android Push Settings"
 [63]: {% image_buster /assets/img/unity/android/unity_android_full_push_listener.png %} "Android Full Listener Example"
-[64]: {{site.baseurl}}/developer_guideplatform_integration_guides/unity/push_notifications/adm_push_notifications/
+[64]: {{site.baseurl}}/developer_guide/platform_integration_guides/unity/push_notifications/adm_push_notifications/

_docs/_developer_guide/platform_integration_guides/unity/sdk_integration/ios.md

@@ -60,7 +60,7 @@ Braze should now be collecting data from your application, and your basic integr
 
 To extend the SDK's behaviors, fork the [Braze Unity SDK GitHub project](https://github.com/appboy/appboy-unity-sdk) and make your required changes.
 
-To publish your modified code as a Unity package, see our [Advanced use cases]({{site.baseurl}}/developer_guide/platform_integration_guides/unity/Advanced_Use_Cases/advanced_use_cases).
+To publish your modified code as a Unity package, see our [Advanced use cases]({{site.baseurl}}/developer_guide/platform_integration_guides/unity/advanced_use_cases/).
 
 ### Transitioning from manual to automated integration (iOS)
 

_docs/_developer_guide/platform_integration_guides/web/google_tag_manager.md

@@ -162,7 +162,7 @@ When implementing the [standard feed UI]({{site.baseurl}}/developer_guide/platfo
 
 #### Custom feed UI
 
-For [custom feed](((site.baseurl))/developer_guide/platform_integration_guides/web/content_cards/customization/custom_styling) styling, the steps are the same as if you had integrated the SDK without GTM. For example, if you want to customize the width of the Content Card feed, you can paste the following into your CSS file:
+For [custom feed]({{site.baseurl}}/developer_guide/platform_integration_guides/web/content_cards/customization/custom_styling) styling, the steps are the same as if you had integrated the SDK without GTM. For example, if you want to customize the width of the Content Card feed, you can paste the following into your CSS file:
 
 {% raw %}
 ```css

_docs/_developer_guide/platform_integration_guides/xamarin/inapp_messages.md

@@ -24,7 +24,7 @@ In-app messages will work by default if you've included the Appboy.bundle folder
 
 See the [iOS integration instructions][1] for information on In-app best practices. Furthermore, you can look at the [sample application][2] for implementation samples.
 
-[1]: {{site.baseurl}}/developer_guide/platform_integration_guides/ios/in-app_messaging/#in-app-messaging
+[1]: {{site.baseurl}}/developer_guide/platform_integration_guides/ios/in-app_messaging/overview/
 [2]: https://github.com/braze-inc/braze-xamarin-sdk/tree/master/appboy-component/samples
 [11]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/in-app_messaging/overview/
 [12]: https://github.com/braze-inc/braze-xamarin-sdk/tree/master/appboy-component/samples

_docs/_developer_guide/platform_integration_guides/xamarin/news_feed.md

@@ -34,7 +34,7 @@ ABKFeedViewControllerModalContext m = new ABKFeedViewControllerModalContext ();
 this.PresentViewController (m, true, null);
 ```
 
-[1]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/news_feed/#news-feed
+[1]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/news_feed/integration/
 [2]: https://github.com/braze-inc/braze-xamarin-sdk
 [11]: {{site.baseurl}}/developer_guide/platform_integration_guides/ios/news_feed/
 [12]: https://github.com/braze-inc/braze-xamarin-sdk/tree/master/appboy-component/samples

_docs/_developer_guide/platform_wide/analytics_overview.md

@@ -385,7 +385,7 @@ If only a single generic name field exists for a user (e.g., 'JohnDoe'), you can
 
 [4]: {{site.baseurl}}/developer_guide/platform_wide/analytics_overview/#purchase-events--revenue-tracking
 [8]: {% image_buster /assets/img_archive/custom_event_analytics_example.png %} "custom_event_analytics_example.png"
-[9]: {{site.baseurl}}/developer_guide/rest_api/user_data/#user-data
+[9]: {{site.baseurl}}/api/endpoints/user_data/
 [10]: {{site.baseurl}}/api/endpoints/messaging/
 [11]: http://www.regextester.com/pregsyntax.html
 [12]: #integers

_docs/_developer_guide/platform_wide/tv_and_ott.md

@@ -247,7 +247,7 @@ Read more about custom handling messaging:
 [3]: {{site.baseurl}}/developer_guide/platform_integration_guides/roku/in-app_messaging/overview/
 [4]: https://github.com/braze-inc/braze-swift-sdk
 [5]: https://designguidelines.withgoogle.com/android-tv/patterns/notifications.html
-[6]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android_tv_push/
+[6]: {{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/android_tv_push/
 [7]: https://developer.amazon.com/docs/fire-tv/notifications.html#headsup
 [8]: {{site.baseurl}}/developer_guide/platform_integration_guides/web/smart_tvs/
 [android-tv-html]: https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#2310

_docs/_help/help_articles/account/locked_out.md

@@ -21,7 +21,6 @@ You can tell what kind of lock out you're experiencing by the error message you
 ## Password error
 
 Your account security is important to us, so passwords are required to log into your Braze account.	
-
 - Check that you are logging into the correct [Braze dashboard instance][1]. Check with your account administrator or Braze account manager to be sure.	
 - Your password may have expired, so you'll need to [reset it][2].	
 - If you use a [single sign-on][3] service, check with your account administrator that the set up has been completed properly.