braze-inc · josh-mccrowell-braze · Jan 13, 2025 · Jan 13, 2025 · Jan 13, 2025 · Jan 13, 2025
diff --git a/_docs/_contributing/troubleshooting.md b/_docs/_contributing/troubleshooting.md
@@ -54,9 +54,9 @@ Learn how to use Liquid's &#123;% raw %} &#123;&#123; page_title }} &#123;% endr
 {% endtab %}
 {% endtabs %}
 
-## Rake: Destination is shared by multiple files
+## Conflict: Destination is shared by multiple files
 
-If `rake` throws the following error, this means that two or more files are sharing the same [`permalink` YAML value]({{site.baseurl}}/contributing/yaml_front_matter/metadata/#permalink).
+If `rake` throws the following warning, this means that two or more files are sharing the same [`permalink` YAML value]({{site.baseurl}}/contributing/yaml_front_matter/metadata/#permalink).
 
 ```bash
 Conflict: The following destination is shared by multiple files.
@@ -66,6 +66,10 @@ Conflict: The following destination is shared by multiple files.
                      - /Users/USERNAME/braze-docs/_docs/_developer_guide/platforms/firos.md
 ```
 
+{% alert note %}
+Although the warning appears after running `rake`, it's actually generated by Jekyll, our static-site generator. For more information, refer to [Jekyll GitHub: Issue #8522](https://github.com/jekyll/jekyll/issues/8522).
+{% endalert %}
+
 To fix this, change the `permalink` value of one of the files, so they're no longer set to the same URL. For example:
 
 {% tabs local %}

diff --git a/_docs/_developer_guide/debugging.md b/_docs/_developer_guide/debugging.md
@@ -15,14 +15,16 @@ The SDK Debugger is currently in beta. Reach out to your account team to enable
 
 ## Prerequisites
 
-To use the Braze SDK debugger, either ensure your native SDKs are up to date with at least these minimum versions, or your wrapper SDKs point to these minimum versions: 
+To use the Braze SDK debugger, you'll need `View PII` and `Export User Data` permissions. Additionally, your Braze SDK needs to meet or point to the following minimum versions: 
 
 {% sdk_min_versions swift:10.2.0 android:32.1.0 %}
 
-To enable debugging for the Braze Web SDK, you can [use a URL parameter]({{site.baseurl}}/developer_guide/platform_integration_guides/web/initial_sdk_setup/#logging) instead.
-
 ## Debugging the Braze SDK
 
+{% alert tip %}
+To enable debugging for the Braze Web SDK, you can [use a URL parameter]({{site.baseurl}}/developer_guide/platform_integration_guides/web/initial_sdk_setup/#logging).
+{% endalert %}
+
 ### Step 1: Close your app
 
 Before you start your debugging session, close the app that's currently experiencing issues. You can relaunch the app at the start of your session.

diff --git a/_docs/_developer_guide/platforms/legacy_sdks/ios/push_notifications/integration.md b/_docs/_developer_guide/platforms/legacy_sdks/ios/push_notifications/integration.md
@@ -30,21 +30,9 @@ noindex: true
 
 # Push integration
 
-## Step 1: Configure push notifications
+## Step 1: Upload your APNs certificate
 
-Before you can send an iOS push notification using Braze, you must provide your `.p8`  push notification file provided by Apple. As described on the Apple [developer documentation](https://developer.apple.com/documentation/usernotifications):
-
-1. In your Apple developer account, go to [**Certificates, Identifiers & Profiles**](https://developer.apple.com/account/ios/certificate).
-2. Under **Keys**, select **All** and click the add button (+) in the upper-right corner.
-3. Under **Key Description**, enter a unique name for the signing key.
-4. Under **Key Services**, select the **Apple Push Notification service (APNs)** checkbox, then click **Continue**. Click **Confirm**.
-5. Note the key ID. Click **Download** to generate and download the key. Make sure to save the downloaded file in a secure place, as you cannot download this more than once.
-6. In Braze, go to **Settings** > **App Settings** and upload the `.p8` file under **Apple Push Certificate**. You can upload either your development or production push certificate. To test push notifications after your app is live in the App Store, its recommended to set up a separate workspace for the development version of your app.
-7. When prompted, enter your app's [bundle ID](https://developer.apple.com/documentation/foundation/nsbundle/1418023-bundleidentifier), [key ID](https://developer.apple.com/help/account/manage-keys/get-a-key-identifier/), and [team ID](https://developer.apple.com/help/account/manage-your-team/locate-your-team-id), then click **Save**.
-
-{% alert note %}
-If you are using the [older navigation]({{site.baseurl}}/navigation), you can upload your `.p8` file from **Manage Settings** > **Settings**.
-{% endalert %}
+{% multi_lang_include developer_guide/swift/apns_certificate.md %}
 
 ## Step 2: Enable push capabilities
 

diff --git a/_docs/_developer_guide/platforms/react_native/push_notifications.md b/_docs/_developer_guide/platforms/react_native/push_notifications.md
@@ -78,13 +78,7 @@ Note that you will need to use these settings instead of the native setup instru
 {% endtab %}
 
 {% tab Android Native %}
-If you are not using the Braze Expo plugin, or would like to configure these settings natively instead, register for push by referring to the following steps from the [Native Android push integration guide]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/?tab=android/):
-
-1. [Add Firebase to your project]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/integration/standard_integration/#step-1-add-firebase-to-your-project).
-2. [Add Cloud Messaging to your dependencies]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/integration/standard_integration/#step-2-add-cloud-messaging-to-your-dependencies).
-3. [Create a service account]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/integration/standard_integration/#step-3-create-a-service-account).
-4. [Generate JSON credentials]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/integration/standard_integration/#step-4-generate-json-credentials).
-5. [Upload your JSON credentials to Braze]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/integration/standard_integration/#step-5-upload-your-json-credentials-to-braze).
+If you are not using the Braze Expo plugin, or would like to configure these settings natively instead, register for push by referring to the [Native Android push integration guide]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/?tab=android/).
 {% endtab %}
 
 {% tab iOS Native %}
@@ -162,15 +156,15 @@ To learn more about what deep links are, see our [FAQ article]({{site.baseurl}}/
 
 {% tabs local %}
 {% tab Android Native %}
-For Android, setting up deep links is identical to [setting up deep links on native Android apps]({{site.baseurl}}/developer_guide/platform_integration_guides/android/push_notifications/android/integration/standard_integration#step-4-add-deep-links).
+If you're using the [Braze Expo plugin]({{site.baseurl}}/developer_guide/platforms/react_native/sdk_integration/?tab=expo#step-2-choose-a-setup-option), you can handle push notification deep links automatically by setting `androidHandlePushDeepLinksAutomatically` to `true` in your `app.json`.
 
-If you are using the Expo plugin and want Braze to handle push deep links automatically, set `androidHandlePushDeepLinksAutomatically: true` in your `app.json`.
+To handle deep links manually instead, refer to the native Android documentation: [Adding deep links]({{site.baseurl}}/developer_guide/platforms/android/push_notifications/#step-4-add-deep-links).
 
 {% endtab %}
 {% tab iOS Native %}
 #### Step 3.1: Store the push notification payload on app launch
 {% alert note %}
-If you are using the Braze Expo plugin, step 3.1 is handled automatically, and you may skip to step 3.2.
+Skip step 3.1 if you're using the Braze Expo plugin, as this is functionality is handled automatically.
 {% endalert %}
 
 For iOS, add `populateInitialPayloadFromLaunchOptions` to your AppDelegate's `didFinishLaunchingWithOptions` method. For example:
@@ -212,6 +206,72 @@ Braze.getInitialPushPayload(pushPayload => {
 {% alert note %}
 Braze provides this workaround since React Native's Linking API does not support this scenario due to a race condition on app startup.
 {% endalert %}
+
+#### Step 3.3 Enable Universal Links (optional)
+
+To enable [universal linking](https://www.braze.com/docs/developer_guide/platforms/swift/push_notifications/deep_linking/#linking-handling-customization) support, create a `BrazeReactDelegate.h` file in your `iOS` directory and then add the following code snippet.
+
+```objc
+#import <Foundation/Foundation.h>
+#import <BrazeKit/BrazeKit-Swift.h>
+
+@interface BrazeReactDelegate: NSObject<BrazeDelegate>
+
+@end
+```
+
+Next, create a `BrazeReactDelegate.m` file and then add the following code snippet. Replace `YOUR_DOMAIN_HOST` with your actual domain.
+
+```objc
+#import "BrazeReactDelegate.h"
+#import <UIKit/UIKit.h>
+
+@implementation BrazeReactDelegate
+
+/// This delegate method determines whether to open a given URL.
+///
+/// Reference the `BRZURLContext` object to get additional details about the URL payload.
+- (BOOL)braze:(Braze *)braze shouldOpenURL:(BRZURLContext *)context {
+  if ([[context.url.host lowercaseString] isEqualToString:@"YOUR_DOMAIN_HOST"]) {
+    // Sample custom handling of universal links
+    UIApplication *application = UIApplication.sharedApplication;
+    NSUserActivity* userActivity = [[NSUserActivity alloc] initWithActivityType:NSUserActivityTypeBrowsingWeb];
+    userActivity.webpageURL = context.url;
+    // Routes to the `continueUserActivity` method, which should be handled in your `AppDelegate`.
+    [application.delegate application:application
+                 continueUserActivity:userActivity restorationHandler:^(NSArray<id<UIUserActivityRestoring>> * _Nullable restorableObjects) {}];
+    return NO;
+  }
+  // Let Braze handle links otherwise
+  return YES;
+}
+
+@end
+```
+
+Then, create and register your `BrazeReactDelegate` in `didFinishLaunchingWithOptions` of your project's `AppDelegate.m` file.
+
+```objc
+#import "BrazeReactUtils.h"
+#import "BrazeReactDelegate.h"
+
+@interface AppDelegate ()
+
+// Keep a strong reference to the BrazeDelegate to ensure it is not deallocated.
+@property (nonatomic, strong) BrazeReactDelegate *brazeDelegate;
+
+@end
+
+- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
+{
+  // Other setup code
+
+  self.brazeDelegate = [[BrazeReactDelegate alloc] init];
+  braze.delegate = self.brazeDelegate;
+}
+```
+
+For an example integration, reference our sample app [here](https://github.com/braze-inc/braze-react-native-sdk/blob/master/BrazeProject/ios/BrazeProject/AppDelegate.mm).
 {% endtab %}
 {% endtabs %}
 

diff --git a/_docs/_help/release_notes/2025.md b/_docs/_help/release_notes/2025.md
@@ -13,4 +13,7 @@ guide_menu_list:
   - name: January 7, 2025
     link: /docs/help/release_notes/2025/1_7_25/
     image: /assets/img/braze_icons/snowflake-01.svg
+  - name: February 4, 2025
+    link: /docs/help/release_notes/2025/2_4_24/
+    image: /assets/img/braze_icons/hearts.svg
 ---
diff --git a/_docs/_help/release_notes/2025/2_4_25.md b/_docs/_help/release_notes/2025/2_4_25.md
@@ -0,0 +1,120 @@
+---
+nav_title: February 4, 2025
+page_order: 11
+noindex: true
+page_type: update
+description: "This article contains release notes for 2/4/2025."
+---
+
+# February 4, 2025 release
+
+## Braze Docs improvements
+
+### Contributing Guide
+Our recent updates to the [Contributing Guide]({{site.baseurl}}/contributing/your_first_contribution) makes it easier for non-technical users to contribute to Braze Docs.
+
+### Data and Analytics revamp
+To make it easier for you to find what you're looking for, we separated the articles formerly nested under "Data & Analytics" into [Data]({{site.baseurl}}/user_guide/data) and [Analytics]({{site.baseurl}}/user_guide/analytics). 
+
+### Developer Guide
+We've done a huge cleanup of all docs across the [Braze Developer Guide]({{site.baseurl}}/developer_guide/home), which included merging "how-to's" split across multiple pages into a single page.
+
+There's also a new [SDK reference page]({{site.baseurl}}/developer_guide/references) that lists all of the reference documentation and repositories for each Braze SDK.
+
+#### Unreal Engine Braze SDK
+We migrated and rewrote all content from the Unreal Engine Braze SDK GitHub repository README into its [dedicated section on Braze Docs]({{site.baseurl}}/developer_guide/platforms/unreal_engine/sdk_integration).
+
+## Data flexibility
+
+### API usage dashboard
+
+{% multi_lang_include release_type.md release="General availability" %}
+
+The [API usage dashboard]({{site.baseurl}}/user_guide/analytics/dashboard/api_usage_dashboard) lets you monitor your incoming REST API traffic into Braze to understand your trends within your usage of our REST APIs and to troubleshoot any potential issues.
+
+### Adding tags to custom attributes
+
+{% multi_lang_include release_type.md release="General availability" %}
+
+You can [add tags to a custom attribute]({{site.baseurl}}/user_guide/data/custom_data/custom_attributes#adding-tags) after it's created if you have the "Manage Events, Attributes, Purchases" permission. The tags can then be used to filter the list of attributes.
+
+### Catalog selections and async catalog fields endpoints 
+
+{% multi_lang_include release_type.md release="General availability" %}
+
+The following endpoints are now generally available:
+* [POST: Create Catalog Fields]({{site.baseurl}}/api/endpoints/catalogs/catalog_fields/asynchronous/post_create_catalog_fields)
+* [DELETE: Delete Catalog Field]({{site.baseurl}}/api/endpoints/catalogs/catalog_fields/asynchronous/delete_catalog_field)
+* [DELETE: Delete Catalog Selection]({{site.baseurl}}/api/endpoints/catalogs/catalog_selections/asynchronous/delete_catalog_selection)
+* [POST: Create Catalog Selection]({{site.baseurl}}/api/endpoints/catalogs/catalog_selections/asynchronous/post_create_catalog_selections)
+
+### Using an email address to trigger campaigns or Canvases
+
+{% multi_lang_include release_type.md release="General availability" %}
+
+You can now specify a recipient by email address to trigger your [campaigns]({{site.baseurl}}user_guide/engagement_tools/campaigns/building_campaigns/targeting_users) and [Canvases]({{site.baseurl}}//user_guide/engagement_tools/canvas/create_a_canvas/create_a_canvas/?tab=target%20audience#step-2c-set-your-target-entry-audience).
+
+### Using a phone number to identify a user via the API
+
+{% multi_lang_include release_type.md release="General availability" %}
+
+You can now use a phone number, in addition to an alias and email address, to identify a user through the [`/users/identify` API endpoint]({{site.baseurl}}/api/endpoints/user_data/post_user_identify)
+
+### Getting a SAML trace
+We added [steps on how to obtain a SAML trace]({{site.baseurl}}/user_guide/administrative/access_braze/single_sign_on/set_up#obtaining-a-saml-trace), which helps you resolve issues about SAML SSO with Support more efficiently.
+
+### Region-specific data centers
+As Braze is growing to serve new areas, we've added an [article about Braze data centers]({{site.baseurl}}/user_guide/data/data_centers) to clarify our operational approach.
+
+
+## Unlocking creativity
+
+### Price drop notifications and back-in-stock notifications
+
+{% multi_lang_include release_type.md release="General availability" %}
+
+You can now notify customers when an item is back-in-stock by setting up [back-in-stock notifications]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/catalog_triggers/back_in_stock_notifications) through a Canvas and catalog.
+
+You can also create [price drop notifications]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/catalog_triggers/price_drop_notifications) to notify customers when an item's price has decreased by setting up price drop notifications in a catalog and Canvas.
+
+### Preview for selection 
+
+{% multi_lang_include release_type.md release="General availability" %}
+
+After creating a selection, you can [view what a selection would return]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/selections/#test-and-preview) for either a random user or a specific user.
+
+### Templating catalog items including Liquid 
+
+{% multi_lang_include release_type.md release="General availability" %}
+
+You can [template catalog items that include Liquid]({{site.baseurl}}/user_guide/personalization_and_dynamic_content/catalogs/using_catalogs/#using-liquid).
+
+### Canvas templates
+We added new Canvas templates for [onboarding users with a preferences survey]({{site.baseurl}}/user_guide/engagement_tools/canvas/get_started/braze_templates/preference_survey) and [creating an email sign-up with double opt-in]({{site.baseurl}}/user_guide/engagement_tools/canvas/get_started/braze_templates/email_signup).
+
+### Managing leads with Salesforce Sales Cloud for B2B
+One way B2B marketers can use Braze is through an integration with the Salesforce Sales Cloud. Read more about how to implement this [use case]({{site.baseurl}}/user_guide/getting_started/b2b_use_cases/b2b_salesforce_sales_cloud).
+
+## Robust channels
+
+### Suppression lists
+
+{% multi_lang_include release_type.md release="Beta" %}
+
+[Suppression lists]({{site.baseurl}}/user_guide/engagement_tools/segments/suppression_lists) specify groups of users who will never receive messages. Admins can create suppression lists with segment filters to narrow down a user group the same way you would for segmentation.
+
+## New Braze partnerships
+
+### Constructor - Dynamic content
+[Constructor]({{site.baseurl}}/partners/message_personalization/dynamic_content/constructor) is a search and product discovery platform that uses AI and machine learning to deliver personalized search, recommendations, and browsing experiences for ecommerce and retail websites.
+
+### Trustpilot - Dynamic content
+[Trustpilot]({{site.baseurl}}/partners/message_personalization/dynamic_content/trustpilot) is an online review platform that enables your customers to share feedback and allows you to manage and respond to reviews.
+
+
+## SDK updates
+
+The following SDK updates have been released. Breaking updates are listed below; all other updates can be found by checking the corresponding SDK changelogs.
+
+- [Braze Android SDK 34.0.0](https://github.com/braze-inc/braze-android-sdk/blob/master/CHANGELOG.md#3400)
+    - Updated the minimum SDK version from 21 (Lollipop) to 25 (Nougat).
diff --git a/_docs/_hidden/other/user_archival.md b/_docs/_hidden/other/user_archival.md
@@ -94,7 +94,9 @@ This allows you to:
 
 ### Steps
 
-1. Target users that meet your brand's archival criteria and that you'd like to retain.<br><br>
+1. Target users that meet your brand's archival criteria and that you'd like to retain. For example, you might retain users who:
+    - Last received a message more then 23 weeks ago or have never received a message<br>AND<br>
+    - Last used your app more than 23 weeks ago or had zero sessions in your app<br><br>
       ![Target users that last received any message more than 23 weeks ago, have never received a message from a campaign or Canvas step, last used these apps more than 23 weeks ago, and have used these apps exactly zero times.][2]<br><br>
 2. Set re-eligibility to be a little less than 6 months long.<br><br>
       ![Entry controls with re-eligibility turned on and the re-eligibility window set to 23 weeks.][3]<br><br>

diff --git a/_docs/_partners/data_and_infrastructure_agility/workflow_automation/fivetran.md b/_docs/_partners/data_and_infrastructure_agility/workflow_automation/fivetran.md
@@ -128,7 +128,7 @@ In the [Fivetran dashboard](https://fivetran.com/dashboard), click on **+ Connec
 
 Navigate to your [Google Storage Console](https://console.cloud.google.com/storage/browser) and select the bucket you configured Braze Currents with, and click on **Edit bucket permissions**.
 
-![The Google Storage Console available buckets. Locate a bucket and click the vertical three dot symbol to open the drop down that allows you to edit bucket permissions.]({% image_buster /assets/img/fivetran_edit_bucket_permissions_gcs.png %})
+![The Google Storage Console available buckets. Locate a bucket and click the vertical three dot icon to open the drop down that allows you to edit bucket permissions.]({% image_buster /assets/img/fivetran_edit_bucket_permissions_gcs.png %})
 
 Next, grant `Storage Object Viewer` access to the email from [step 1](#step-one2) by adding the email as a member. Make a note of the bucket name; you will need it in the next step to configure Fivetran.
 

diff --git a/_docs/_user_guide/administrative/app_settings.md b/_docs/_user_guide/administrative/app_settings.md
@@ -62,5 +62,8 @@ guide_menu_list3:
   - name: Custom Data
     link: /docs/user_guide/data/custom_data/managing_custom_data/
     image: /assets/img/braze_icons/database-01.svg
+  - name: Export Logs
+    link: /docs/user_guide/administrative/app_settings/exports_log/
+    image: /assets/img/braze_icons/file-download-02.svg
 
 ---